Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Bug (usability) with custom makefiles and clickable errors
Jenna:
I use Makefile based projects regulary, if I develop for wxWidgets.
I have several flavours of wxwidgets (gtk2, gtk3, dynamic aui-branch for gtk2 and gtk3) and develop in it.
I use a sepearate build-folder (my_build_gtk2, my_build_gtk3) from where I run the configure script and where thge makefiles are generated.
This is a necessary step to create the intermediate files there, of course.
If I get errors or warnings, there aren't any issues jumping to the correct sources.
My projects base-path is the root-path of the sources and the Makefiles execution-dir is my seperate build-folder.
I just tested the same with the C::B automake-stuff and it also works flawlessly.
Calmarius:
And how does CB locate the files? Does it parse and understand the makefile? Searches the filesystem?
MortenMacFly:
--- Quote from: Calmarius on November 21, 2012, 12:57:00 pm ---And how does CB locate the files? Does it parse and understand the makefile? Searches the filesystem?
--- End quote ---
It runs make on your Makefile(s). As simple as that. A Makefile should declare all needed files 7 path's / libs / flags and alike. That's what a Makefile is for. If you Makefile is incomplete, the build will be incomplete. That applied to all other Makefile based projects in the world, with or without IDE.
Calmarius:
There is no problem with the makefile.
The problem is that the makefile changes the working directory during the build. If there is an error or warning, CB stupidly assumes the problematic file is at <makefile_path>/<path_the_gcc_reports> if the working directory changes during the build the path will be incorrect, and I cannot open the file by clicking the error or warning message. The same applies when I try to debug, the IDE cannot open file.
Changing the makefile to make CB happy is not an option.
Jenna:
--- Quote from: Calmarius on January 31, 2013, 02:00:39 pm ---There is no problem with the makefile.
The problem is that the makefile changes the working directory during the build. If there is an error or warning, CB stupidly assumes the problematic file is at <makefile_path>/<path_the_gcc_reports> if the working directory changes during the build the path will be incorrect, and I cannot open the file by clicking the error or warning message. The same applies when I try to debug, the IDE cannot open file.
Changing the makefile to make CB happy is not an option.
--- End quote ---
If you have a proper makefile-based build-system (with incremental makefiles) it works correctly.
Just tried it with C::B's makefile stuff on linux.
If the makefile internally changes the directory, there is no way for C::B to know that (except parsing the makefile's output, but this is obviously not an option).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version