search

christian0101 / svnx

Automatically exported from code.google.com/p/svnx
0 stars 0 forks source link

"Call Subversion libraries directly" is dimmed #98

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Copy svnX to /Developer/Applications
2. Install Subversion 1.6.11 package for Snow Leopard
3. Open Preferences window

What is the expected output? What do you see instead?
The option named "Call Subversion libraries directly" is dimmed. I expect I can 
switch it on.

What version of the product are you using? On what operating system?
1.2 on 10.6.3

Thank you

Original issue reported on code.google.com by florent....@gmail.com on 8 Jun 2010 at 2:03

GoogleCodeExporter commented 8 years ago 
Additional info:
I have added the following line to my .profile:
export PATH=/opt/subversion/bin:$PATH
I even tried to add:
export DYLD_LIBRARY_PATH=/opt/subversion/lib:$DYLD_LIBRARY_PATH
which did not give better result

Original comment by florent....@gmail.com on 8 Jun 2010 at 3:01

GoogleCodeExporter commented 8 years ago 
Unfortunately they broke Subversion 1.6.11 by removing some of the libraries.
SvnX corrects this by adding symbolic links in /opt/subversion/lib to the 
relevant system libs.
The folder /opt/subversion/lib needs to be writable.  (I think it is by 
default.)
Make sure it is, launch svnX, quit & relaunch svnX.
The "Call Subversion libraries directly" should now be available.

Original comment by chris...@gmail.com on 8 Jun 2010 at 4:04

GoogleCodeExporter commented 8 years ago 
Thank you,

the folder opt was not writable (maybe because it was initially created by 
MacPorts)

Original comment by florent....@gmail.com on 9 Jun 2010 at 7:28

GoogleCodeExporter commented 8 years ago 
I have Subversion installed in different place and would like to do this adding 
symbolic links manually.

Please tell me which file to link.

Thanks,
Takeshi

Original comment by kim.take...@gmail.com on 3 Jul 2010 at 2:58

GoogleCodeExporter commented 8 years ago 
I don't know if this will help you as what was broken was the particular 
installation/distribution & NOT Subversion itself.
Anyway, the links are:
    /opt/subversion/lib/libapr-1.0.dylib  ->  /usr/lib/libapr-1.0.dylib
    /opt/subversion/lib/libaprutil-1.0.dylib  ->  /usr/lib/libaprutil-1.0.dylib

If you are trying to get svnX to dynamically link/load a different installation 
you probably want to replace the symbolic links in svnX.app/Contents/Frameworks 
instead.  (As I think I have mentioned previously.)

Original comment by chris...@gmail.com on 3 Jul 2010 at 4:19

GoogleCodeExporter commented 8 years ago 
Thank you Chris, but it did not work as you doubted.

I have the links in .../Frameworks set, but doesn't work.

I also cannot build svnX on OS 10.6.3 and XCode 3.2.2, due to some errors.
Should it be built on snow leopard?

Original comment by kim.take...@gmail.com on 5 Jul 2010 at 5:48

GoogleCodeExporter commented 8 years ago 
Takeshi,

If you want my help you're going to have to provide more information than 
"doesn't work".
[It does work.  It just changed the links to point at the appropriate svn-1.4.4 
libs in /usr/lib and it worked as expected.]

What does `ls -la <your-build-dir>/svnX.app/Contents/Frameworks` output?
Are you still using a MacPorts Subversion installation?

I haven't tried building with Xcode 3.2.x.  SvnX 1.2 was built with Xcode 3.1.4 
on OSX 10.5.8.
What errors do you see?

Original comment by chris...@gmail.com on 5 Jul 2010 at 7:19

GoogleCodeExporter commented 8 years ago 
If app fixes svn libs on launch it now notifies the user notification & offers 
the option to re-launch.
Added in 1.3b1.

Original comment by chris...@gmail.com on 16 Sep 2010 at 12:18