Codebench and Makefiles

6 posts / 0 new

Last post

Sun, 2013-01-27 22:13

cha05e90

Offline

Last seen: 2 years 8 months ago

Joined: 2011-02-07 20:22

Codebench and Makefiles

After fiddeling around with some single source files I decided to put all the #includes, prototypes and defines into a new header file. Codebench did the obvious and wrote a new Makefile (and a new project file as well). After that I were not able to compile anything. After some investigation I found the following: My old (working!) Makefile for the single source file looked like this:

$(BIN): $(OBJ)
#	Debug builds require the -g or -gstabs option in CFLAGS
#	You may also need to move the LDFLAGS variable depending on the contents
	$(CC) $(OBJ) $(LIBS) -o $(BIN) $(CFLAGS) $(LDFLAGS)
	strip $(BIN) -o $(BIN)
 
Example.o: Example.c
	$(CC) -c Example.c -o Example.o $(CFLAGS)

The new generated Makefile for one source and one header file looked like this:

$(BIN): $(OBJ)
#	Debug builds require the -g or -gstabs option in CFLAGS
#	You may also need to move the LDFLAGS variable depending on the contents
	$(CC) -o $(BIN).debug $(OBJ) $(LDFLAGS) $(LIBS)
	strip $(BIN).debug -o $(BIN)
 
Example.o: Example.c header.h
	$(CC) -c Example.c -o Example.o $(CFLAGS)

It doesn't compile, because the "$(CFLAGS)" is missing in the "$(BIN):" part of the new makefile. Further I never specified to do a "Example.debug" binary ("$(BIN).debug"). Any idea where this comes from? AFAIK Codebench uses a standard "make -f" call, but I really don't know where this omitting (or including) of $(CFLAGS) and the binary naming with a ".debug" is controlled...

Mon, 2013-01-28 12:23

Rigo

Offline

Last seen: 1 month 2 weeks ago

Joined: 2011-01-24 21:55

I'd hazzard a guess

I'd hazzard a guess here: http://codebench.co.uk/docs/projectinfo.html#compiler Specifically the "Include debug symbols" part. And the CFLAGS variable is not needed, because they are compiler flags, and the "BIN" rule is actually a job for the linker. Giving the actual error from the make would be a much better way to covey any potential problem. Simon

Mon, 2013-01-28 21:51

(Reply to #2) #3

cha05e90

Offline

Last seen: 2 years 8 months ago

Joined: 2011-02-07 20:22

Hello Simon! Thanks for that

Hello Simon! Thanks for that very useful hint about the linker vs. compiler switches. I had accidentally put the usual "-lauto" etc. into the compiler switches instead of the linker section. So now it compiles just nice, BUT - I still get two executables: one with ".debug" extension and one normal, which seems to be the "stripped" version of the debug exe. Is this the normal Makefile and executable output? BTW: My settings window doesn't show the contents of your linked window (no "Include Debug Symbols" here...Codebench v0.23)?!?

X1000|II/G4|440ep|2000/060|2000/040|1000

Tue, 2013-01-29 01:44

(Reply to #3) #4

Rigo

Offline

Last seen: 1 month 2 weeks ago

Joined: 2011-01-24 21:55

Hmmm, well that oversight wil

Hmmm, well that oversight wil be fixed in the next public version. It is normal practice to create an executable compiled with debug symbols that is useful for debugging during development. This is then "stripped" to create a release executable. All the makefile is doing is automating that for you, nothing to worry about. Simon

Tue, 2013-01-29 10:23

(Reply to #4) #5

cha05e90

Offline

Last seen: 2 years 8 months ago

Joined: 2011-02-07 20:22

Excellent, thanks for that

Excellent, thanks for that answer!

X1000|II/G4|440ep|2000/060|2000/040|1000

Sun, 2013-02-03 15:40

(Reply to #5) #6

hypex

Offline

Last seen: 1 day 5 hours ago

Joined: 2011-09-09 16:20

I'm looking forward to the

I'm looking forward to the new version. I tried to use CodeBench to create a makefile from a fairly large set of sources. But all it does is slowly add the sources (this is an X1000) and then crash leaving me with a blank makefile. Perhaps less annoying is the bug where I add sources for a new project and the build icon is ghosted out.

Search form

User login