User forums > Using Code::Blocks

Code::Blocks + MingGW doesn't link static lib.. HELP !

<< < (3/3)

MortenMacFly:

--- Quote from: oBFusCATed on January 24, 2010, 02:50:10 pm ---The question is can we implement it reliably?  :lol:

--- End quote ---
I honestly believe no.


--- Quote from: oBFusCATed on January 24, 2010, 02:50:10 pm ---And what are the possible problems?

--- End quote ---
Well - try to do it (configurable) for a number of (partially unknown) compilers (think f copies of compilers) and platform depended. So the same compiler on another platform will have different dependencies. Try to work out a concept and you most likely will fail. It works for MS because they have one compiler and one platform. It's easy to do it that way. But if you really come up with a good approach... I am very interested in hearing it!

Feneck91:
I make dependencies on libs and all work fine ! I just ask some question to find way to resolve problems that I know how to resolve in Visual C++ compiler, not to launch stones on Code::Blocs... Really, I'm very surprise by the quality of Code::Blocks IDE, good job for everyone to have made this very good complier environment !
Thanks to all contributors.

For this problem : I modify the .h of a lib, the lib is re-build an exe link again. I modify the .cpp of a lib, the lib is re-build but the exe is considered up to date and so is not linked again. I have added dependencies with all .a (lib) that the exe used and all work fine now.

MortenMacFly:

--- Quote from: Feneck91 on January 24, 2010, 06:09:40 pm ---I have added dependencies with all .a (lib) that the exe used and all work fine now.

--- End quote ---
That's exactly the steps you had to do. :-)

TerryP:

--- Quote from: MortenMacFly on January 22, 2010, 02:14:30 pm ---
--- Quote from: Feneck91 on January 22, 2010, 01:25:11 pm ---I'm working for 15 years in Visual C++ and all these libraries are included by the wizard, that why I don't know :
The order of the library is important for linking...

--- End quote ---
See: That is exactly why I hate VS. It gives you no in-sight, makes some hocus-pocus and it somehow works as the VS compiler/linker probably is tweaked accordingly. However, once you want to port or switch to another build system you are in hell.

--- End quote ---

Not to drift off topic, but that really is a user problem, not a visual studio problem.

Code::Blocks has wizards of it's own that try to setup certain properties for a new project. There's no real difference... the question is who has the balls to ask, "Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?" with a straight face. Any decent programmer should know how the build and runtime system for their language environment works, I still know plenty who can't tell a cmd window from a tutorial. The biggest difference between C::B and Microsoft's IDE, is the former adapts itself to tool bundles, while the latter integrates itself with its tools.

The only real differences I've found between the two, is Code::Blocks lacks inheritable property sheets, and has a much more logical layout for setting build options.

Navigation

[0] Message Index

[*] Previous page