It would be great if there was some option not to use
the dev-cpp generated Makefile.win, instead to be able
to specify a Makefile for building.
dev-cpp doesnt have the ability at this stage to
handle the GNU-style package I'm developing, so I
generate a configure script and Makefile pair from
autoconf and automake. Unfortunately this means a
lot of console editing (vim for m4 files), building
(./configure make), and debugging (gdb). It would be
nice to be able to do the debugging within the IDE,
and all it would require is the ability to specify a
custom Makefile: leave the user to ensure that -g or
equivalent is added.
Logged In: YES
user_id=729888
This would be increbily useful.
I've spent a long amount of time editing Makefiles today.
I have had Dev-C++ installed on 2 drives in 3 locations now.
When I compile and run the makefile has the wrong drive and
the wrong path for everything. The original installation.
I haven't been able to find a way to change this as yet... I
haven't really looked though.
I found that adding a nice little "PATH = C:/Dev-Cpp/.../..."
and then adding a nice little $(PATH) before all of your
file names.
e.g.
main.o: $(PATH)main.cpp
$(CPP) -c $(PATH)main.cpp -o $(PATH)main.o $(CXXFLAGS)
This saves a lot of time when you have to recompile, as long
as you remember to update any libs needed etc.
Also, remember to rename it to something other than
Makefile.win it'll just get overwritten when you press F9
through force of habit.
Compilation is simple enough using make.exe in the 'bin' dir
of your Dev-Cpp root directory.
"make.exe -f "C:/Dev-Cpp/.../.../WorkingMakefile.win" all"
No problems.
Hope this is of some use to someone, sometime.
Logged In: YES
user_id=322885
Being able to use a custom makefile would be very useful
indeed, because hand-made makefiles can be more flexible and
powerful.