Code::Blocks Forums

User forums => Help => Topic started by: r.stiltskin on April 22, 2008, 07:18:50 pm

Title: first experience with nightly builds
Post by: r.stiltskin on April 22, 2008, 07:18:50 pm
I've been using (& loving) code::blocks 8.02 for a couple of weeks & would like to try upgrading with nightlies.  I have a few questions:

1:
I checked out #5010 and ran ./bootstrap.  It returned this message (I guess from automake):
You should add the contents of '/usr/share/aclocal/libtool.m4' to 'aclocal.m4'.
Really??  What does that mean -- I should append libtool.m4 to aclocal.m4?

2:
After I run ./configure and make, will "make install" (as root) just overwrite the existing ver. 8.02 files with any files that changed, or is there something else I have to do?
Will I still have the plugins that are installed in 8.02 or will I have to install them separately?

The instructions on the Nightly Builds forum seem to be for Windows only.
The only CURRENT Linux-relevant instructions I found were here:
http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Linux
Is there anything else I should read as an introduction to the current nightly-build setup?
Title: Re: first experience with nightly builds
Post by: mandrav on April 22, 2008, 07:39:53 pm
Quote from: r.stiltskin on April 22, 2008, 07:18:50 pm
1:
I checked out #5010 and ran ./bootstrap.  It returned this message (I guess from automake):
You should add the contents of '/usr/share/aclocal/libtool.m4' to 'aclocal.m4'.
Really??  What does that mean -- I should append libtool.m4 to aclocal.m4?

You can ignore that most of the times.

Quote from: r.stiltskin on April 22, 2008, 07:18:50 pm
2:
After I run ./configure and make, will "make install" (as root) just overwrite the existing ver. 8.02 files with any files that changed, or is there something else I have to do?
Will I still have the plugins that are installed in 8.02 or will I have to install them separately?

if you run configure with "--prefix=/usr" then it will overwrite 8.02. By default (i.e. if you don't pass that option) it installs under /usr/local.

As for the plugins, if you want to build them all, you need to pass "--with-contrib-plugins=all" in the configure command line.
Really, just type "./configure --help"...
Title: Re: first experience with nightly builds
Post by: r.stiltskin on April 22, 2008, 11:24:58 pm
Thanks.  I ran configure using "--with-contrib-plugins=all" & let it install to /usr/local.

make install seemed to compled successfully, but the debugger and the codesnippets plugins were not installed.  When I open code::blocks there is an warning pop-up saying that one or more plugins were not loaded, listing libdebugger.so and libcodesnippets.so & saying "check the application log" for more information, and something about them being built for a different version of Code::Blocks.

Which log?  I can't find any *codeblocks*.log in /var/log or in /usr/local.

Did I omit something, or is something wrong with the nightly?
Title: Re: first experience with nightly builds
Post by: ouch on April 22, 2008, 11:48:21 pm
did you run the batch file to finalize the compilation process?
Title: Re: first experience with nightly builds
Post by: r.stiltskin on April 22, 2008, 11:57:05 pm
Quote from: ouch on April 22, 2008, 11:48:21 pm
did you run the batch file to finalize the compilation process?
Which batch file?
Title: Re: first experience with nightly builds
Post by: ouch on April 23, 2008, 12:21:55 am
update.bat for windows or simply update for linux users.

there both in the src folder.
Title: Re: first experience with nightly builds
Post by: r.stiltskin on April 23, 2008, 12:33:49 am
Hmmm... a brief README in trunk would be helpful.

after cd to the src directory I ran ./update.  Here's the output:
Code
Creating output directory tree
Compressing core UI resources
Compressing plugins UI resources
Packing core UI bitmaps
Packing plugins UI bitmaps
Copying files
cp: cannot stat `devel/codeblocks': No such file or directory
cp: cannot stat `devel/*.so': No such file or directory
cp: cannot stat `devel/share/codeblocks/plugins/*.so': No such file or directory
Creating launch-scripts
True, there is no devel/codeblocks.
There are no devel/*.so files.
devel/share/codeblocks/plugins is an empty directory.

What next?
Title: Re: first experience with nightly builds
Post by: ouch on April 23, 2008, 02:42:58 am
it sounds like you didn't read either the BUILD file included in the SVN, or the more in depth wiki located at the top of the forums.

I recommend forgeting the build file and going strait to the wiki myself.
Title: Re: first experience with nightly builds
Post by: r.stiltskin on April 23, 2008, 03:53:15 am
Quote from: ouch on April 23, 2008, 02:42:58 am
it sounds like you didn't read either the BUILD file included in the SVN, or the more in depth wiki located at the top of the forums.

I recommend forgeting the build file and going strait to the wiki myself.
Actually I read whatever I could find that seemed relevant.

The wiki "important changes to the nightly builds" at the top of the Nightly Builds forum only talks about windows so that doesn't help.
The wiki "How to use a nightly build" which is right below that was written in May 2006 and talks about 7-zipped binary distributions and RC2, so that one seems pretty obsolete.
I don't see any others.  Which one are you recommending?

All the BUILD file says regarding building in Linux is:
Code
Unix build instructions:
------------------------
You need a working autotools environment (autoconf, automake, libtool, make, etc).
In a terminal, go to the top level folder.
If you fetched the sources from SVN, you need to bootstrap the program first. So type:

./bootstrap

This will adapt the project's configuration file to your environment. This only needs to be done once: the first time you checkout the SVN version.

After this, type the following:

./configure --enable-contrib
make
make install

For the last step you must be root.
That's it.
I did everything mentioned there.  I don't see anything there that applies to this plugins problem.

If you know of something that I have overlooked, please point me to it.  Thanks.
Title: Re: first experience with nightly builds
Post by: ouch on April 23, 2008, 04:26:16 am
your looking for "Installing Code::Blocks" in a large font in the center of your screen when you open the wiki up. :lol:

talks about setting up for several platforms.
Title: Re: first experience with nightly builds
Post by: r.stiltskin on April 24, 2008, 04:38:39 pm
It sounds like you didn't read my original post, where I said that that wiki was the only current linux-relevant information I found.  :P

That update script is not even mentioned in the wiki -- I'm not sure what its purpose is as it contains no comments, but I suspect it's there to be used by the developers since it's zipping a lot of files in a directory called "devel" which is not included among the files that svn checks out.

Since I did exactly what the wiki says to compile code::blocks along with all of the plugins to the default install directory, I wonder if there may have been something wrong with build #5010.  I just finished installing build #5016 on a different computer using exactly the same command & it worked perfectly.  When I return to my other location I'll try the first one again with a new build & see what happens.
Title: Re: first experience with nightly builds
Post by: stahta01 on April 25, 2008, 03:41:53 pm
update.bat and update is used when the user compiles code::blocks using code::blocks. I do not think it is used when using configure/make method.

Can you repeat what Linux Distro and Version you are using? Maybe a prereq is missing.

Tim S
Title: Re: first experience with nightly builds
Post by: Biplab on April 25, 2008, 05:17:58 pm
Quote from: ouch on April 23, 2008, 12:21:55 am
update.bat for windows or simply update for linux users.

there both in the src folder.

This is not applicable for Linux if you're using configure and make.

Quote from: r.stiltskin on April 22, 2008, 11:24:58 pm
Which log?  I can't find any *codeblocks*.log in /var/log or in /usr/local.

Check them under the .codeblocks dir inside your home folder.
Title: Re: first experience with nightly builds
Post by: r.stiltskin on April 26, 2008, 07:47:47 pm
I'm using Kubuntu Gutsy on the 1st machine & Kubuntu Feisty on the 2nd machine.  Both are fully-updated.   As I said before, on the 2nd machine I installed build #5016 & it went perfectly.  Today, I'm back at the 1st machined and I have installed Build #5020 (configured the same as the first time, using ./config --with-contrib-plugins=all ) and this time it installed perfectly here as well.  So I conclude that there must have been some error(s) in build #5010 but it seems to be irrelevant now since whatever it may have been, it has been fixed.

I'm still curious about the log that is mentioned in the plugin warning message (post #3).  I looked in ~/.codeblocks and its subdirectories & find no logs there either.  The only log I found related to this project is the obsolete ChangeLog (which I think the developers should delete) included in the checkout files and the autoconf config.log located in trunk.   And the only errors I notice in that file are:
Code
configure:4356: gcc -E  conftest.c
conftest.c:10:28: error: ac_nonexistent.h: No such file or directory
and
Code
configure:7075: g++ -E  conftest.cpp
conftest.cpp:21:28: error: ac_nonexistent.h: No such file or directory
I don't think they have anything to do with the plugin problem.

Is there another log that I'm not finding?