User forums > Using Code::Blocks
Have code::blocks only run 'make'
stahta01:
--- Quote from: dfatcb on January 19, 2016, 09:10:51 am ---I checked that box, but also set the type to script only and also tried native. neither would build?
--- End quote ---
You NEED to pick only one of the options I listed! You can NOT do both at the same time!
If using the "custom makefile" method.
Did you create a makefile or point the project to a makefile?
I would create a new makefile that uses the existing makefile.
You need to tell us which method you are trying to do!
Tim S.
Jenna:
Here is a quote of my answer in another thread:
--- Quote from: jens on September 18, 2010, 01:11:56 pm ---C::B can not convert from makefile to C::B build-system.
This has to be done manually.
The difficulty highly depends on the size and complexity of the project.
But you can create a custom makefile project:
* Create an empty project with the wizard,
* add all files you might want to work on,
* go to "Project -> Properties",
* check "This is a custom makefile",
* edit the makefile name if needed,
* change the path to the makefile if needed,
* fix the make commands in "Project -> Build options -> "Make " commands", for the target and/or the whole project.
--- End quote ---
For nested makefiles, just point to the root-makefile.
If you use the $make-variable, make sure the make-executable in the toolchain you use is correct.
You can also execute configure script or others instead of the make-executables in special targets.
I do it to compile wxWidgets (and me-tv) on my Fedora box and it works smoothly.
dfatcb:
ok, so set compiler to gcc c, and targets console app. changed the make commands to just have two, the "make" and "make clean".
kbuild seems to work. If anyone knows if there is a way to have kbuild output to a different directory, that be great. I use modules now for target, when I tried putting in a directory name, the build would say it does't know how to make the target ?
Navigation
[0] Message Index
[*] Previous page
Go to full version