User forums > Help

Best way to update C::B on Linux from SVN

<< < (3/3)

Jenna:
What's the problem with calling run.sh ?
You should be able to run it from a file-explorer too (I use Thunar from xfce4).

The wrapper script is needed to make C::B find it's libraries on linux.
Alternatively you can add the output-directory to LD_LIBRARY_PATH in the startup-script of your user-account or add it to
--- Code: ---/etc/ld.so.conf
--- End code ---
[/b] or create a *.conf-file in /etc.ld.so.conf.d/ (if it exists) and run ldconfig as root as described in: http://wiki.codeblocks.org/index.php?title=Compiling_Code::Blocks_in_Linux_%28applies_to_all_distros%29#Resolving_issues.
Both alternatives might interfere with other ("normally") installed vesrions of C::B, because they permanently change the search-path for the libraries.

stefanos_:
@jens: I did not say that I dislike using run.sh. All I simply said is, should not update.bat and update scripts behave the same?

What I tend to do with Windows version, is to simply synchronize my svn code with the trunk, open the .cbp and .workspace (windows version of course), compile both of them, and if everything works fine (accordingly to my needs of course), I run the update.bat file to use the latest revision.

All I want is the same procedure for Fedora; to open my Linux .cbp and .workspace files, compile them and run the update script to "upgrade" from an old svn revision to either the latest available one, or the one I manually choose.

I hope I made it clearer now, because I thought my initial question was clear and easy to comprehend.

Jenna:
So I don't see your problem, because it behaves exactly like on windows.

The only difference is that you have to use run.sh instead of codeblocks.exe.

Navigation

[0] Message Index

[*] Previous page