User forums > Help

Moving from makefile to C::B project

<< < (2/2)

visir:
Running command: mingw32-make.exe -f makefile Release
mingw32-make.exe: *** No rule to make target 'Release'.  Stop.

How to rename or create build target?

BlueHazzard:
Project->Properties->Build targets

this is not sooo complicated to not make it as a cb project.... but using the makefile would be easier, also to keep in sync with the official repo

[EDIT: the path is "Project->Properties->Build targets" not "Project->Build targets"

visir:
New problem: codeblocks runs make from windows terminal, while I only run it from msys2 terminal. Commands like mkdir are now broken, they require \ instead of / as path separator. I need to rewrite makefile now.

Maybe I'll actually move to codeblocks project after all. I need to understand what are those "build scripts" and "Pre/post build steps" with "custom variables" first. And if I can recreate some sort of logic and variables in those prebuild steps.

BlueHazzard:
You can set the make program codeblocks uses with

Settings->Compiler->Global compiler settings->Toolchain executables->Make program

note you probably have to click on the white right arrow on the right side of the dialogue to make the "Toolchain executables" tab visible


--- Quote ---Maybe I'll actually move to codeblocks project after all. I need to understand what are those "build scripts" and "Pre/post build steps" with "custom variables" first. And if I can recreate some sort of logic and variables in those prebuild steps.
--- End quote ---
the wiki is your friend. And note also you can use squirrel scripting, so you have a touring complete programming language on your side to do wired things with the build system. You can use the scripting language also for compiler/ linker options, and i think you can also outsource all this in a script file

Navigation

[0] Message Index

[*] Previous page