User forums > Using Code::Blocks
C::B new releases hung on linkage in cygwin
littlegene:
Here is the "test" project
Suppose, it consists of one dummy main.cpp (superfluous) executable and 2 librariers that have to be built as well.
One library named "replace" provided as a sample of good build even in the case Morten McFly modifies the PATH env var in C::B (incl. for "custom" makefile).
The other is an "xml-rpc" lib that is successfully built only inside cygwin console with native, unmodified PATH. "xml-rpc" lib, however, hangs when
building goes via a PATH that is modified in C::B.
You should have in the most recent Cygwin (now 1.7.16):
1. autotools (libtool, automake, autoconf)
2. make utility
3. g++ 4 version of compiler
4. Maybe something else...
Step-by-step after unpacking the test project to a cygwin user directory:
1. Execute cygwin console and go to the project directory
2. sh bootstrap
Now configure script is ready
3. sh runconfigure
Now makefiles all over the directories are ready
4. make all
You should see on entering (or exiting) each particular build directory the current right value of PATH env variable
You should also see that all executables (replace, xml-rpc, and main ) are compiled and built fine.
Step-By-step for building through the custom makefiles (obtained before) in C::B
1. Move testp.conf into the /Users/<user>/AppData/Roaming/codeblocks.
2. With the most recent C::B (eg. rev. 8394) open the testp.cbp project files:
codeblocks /p=ask (choose testp personality)
3. Open testp project (please ignore offers of START PAGE)
4. Correct compiler and linker disk settings already written in, compiler path, ...
I suppose, testp project has custom makefile and compiler full log turned on.
5. Choose MAKEALL build target and Press Ctrl+F11
The project should start rebuilding and during this process you can see current value of PATH env variable at build log as well.
My question is whether the xml-rpc in hung now on your own ? And what do you observe in the PATH value output at build log?
(PATH value now (in 8394 rev) is almost (not fully, as it was in 7801 rev) correct, but the author added (in 7802 rev) '/' directory that breaks the build :'()
MortenMacFly:
--- Quote from: littlegene on September 19, 2012, 01:05:39 pm ---Here is the "test" project
--- End quote ---
It fails to compile/configure, as all sub-folders are empty. Isn't it possible to reduce it to a minimal hello world example? W/O the need of bootstrap, auto-foo and alike?
MortenMacFly:
...btw: I can debug anything compiled with Cygwin just fine (on windows). hence I am using a proper non-makefile based project file and the default debugger. I just set a BP in your (Cygwin based) hello world app and it stopped there just fine.
Maybe you are doing things too complicated?! I mean: You have an IDE here, use its power!
littlegene:
Thank you for your reply.
The correct test project will be posted (size < 128k) tomorrow again. If it is not time consuming, please check it then.
I am rather doubt in my mind: None of things you wrote does not work at me:
1. I prefer use autotools and need a outer makefile (and of course in tha same project I also have several native C::B build targets (specially for debug purpose) which are completely nice )
2. I have to apply (each time) well known patches for gdb in cygwin and force C::B to really work in debugging
3. Now cygwin has a problem that establishing BP in mount-like style (as C::B does: /cygdrive/c/cygwin/home/user/....) succeeds only if debugging project is on the other logical disk that Cygwin deploy folder...
(for item 3: I have (checked) 3 computers with that state : one job computer and 2 notebooks )
How you succeed in these 3 things - enigma for me )
talk to this place later.
thanks, again.
littlegene:
--- Quote from: MortenMacFly on September 21, 2012, 07:26:09 pm ---
--- Quote from: littlegene on September 19, 2012, 01:05:39 pm ---Here is the "test" project
--- End quote ---
It fails to compile/configure, as all sub-folders are empty. Isn't it possible to reduce it to a minimal hello world example? W/O the need of bootstrap, auto-foo and alike?
--- End quote ---
Unfortunately, autotools withdrawal is quite complicated for me... And Hello world example always compiles fine. Remember: we have to watch the situation then C::B PATH env var substitution *influences* on cygwin compilation bugs in some cases.
Adusted test project is right underneath.
Again, please use
sh bootstrap
sh runconfigure
make all
and after that, check "make all" (for testp.cbp) in C::B...
[attachment deleted by admin]
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version