User forums > Help

rev 7954 screwsup big time

<< < (3/4) > >>

oBFusCATed:

--- Quote from: killerbot on May 09, 2012, 01:29:12 pm ---Same when one would build by using the cbp's files. Then you actually don't know what bootstrap/configure is ;-), you build and call update.

when "make" or "pressing build button" in CB is not sufficient to build (when no new plug-ins,libraries are added), plain simple : build system is wrong.

--- End quote ---
The difference is that the ./configure handles many systems and handles dependencies, C::B's build system doesn't.
I don't know what has happened on your system, probably some dependencies are not handled. If you can reproduce the problem we can try to fix it.
Probably update back to r7920, do a full clean build, update again and do another build with make only.
Also keep in mind that make uninstall is pretty useless...

I generally follow the boostrap/configure/make/make install command chain, when I want create installable versions of C::B and I have no problems.
I do this in order to get a reliable version of C::B.

And after an update I always do a full rebuild even using C::B's build system, just in case.

Another thing, it is always better to build packages for the distribution you're on instead of using make/make install directly.
I do this both on gentoo (where I have an svn ebuild) and on centos(where I use rpmbuild to build rpms).
I guess Jens could post the steps needed to build debian packages.
This is the most reliable way to install software on linux. If you don't like it use windows or macosx (the drag and drop territory).

p.s. you reminded me that I've forgotten to fix the Makefile.am in my last commit...

MortenMacFly:

--- Quote from: killerbot on May 09, 2012, 01:29:12 pm ---Probably update back to r7920, do a full clean build, update again and do another build with make only.

--- End quote ---
Maybe its even easier: Just pump the SDK version temporarily, hit make (only) and have a look if it fails at runtime. I have that weird feeling that this is the root of the evil.

Jenna:

--- Quote from: oBFusCATed on May 09, 2012, 01:55:56 pm ---I guess Jens could post the steps needed to build debian packages.

--- End quote ---
dpkg-buildpackage in the root of C::B's (svn-)sources (the folder where the debian subfolder is).
The debs are in the folder wher C::B's root folder is located.
You might need to run ./update_revision.sh to update debian/changelog to have the correct svn-version in the packagenames.

daniloz:
Sorry for the (bit) OT question, but...

Is there a way to do anything similar to a "command-line linux make" in Windows to build C::B (core project and plugins project) after an svn update? I mean, just opening a console and typing something like "make" to do the whole process.

You can assume that I have both cygwin and msys running on my system. :-)

oBFusCATed:
If you have working codeblocks, you should be able to use it in batch mode.
Otherwise there was a patch for the autotools system for building mingw32 binaries on linux.
I guess you can search for it and see if it makes the autotools system usable under cygwin, but I doubt it.

Navigation

[0] Message Index

[#] Next page

[*] Previous page