Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
SDK refactoring for non UI builds
killerbot:
--- Quote from: oBFusCATed on September 02, 2012, 05:01:34 pm ---
--- Quote from: MortenMacFly on September 02, 2012, 04:30:43 pm ---Also, for these things I wonder why people don't simply use i.e. the Makefile generator available for Code::Blocks. OK - it won't be scriptable and alike, but would you need it for such special cases?
--- End quote ---
Because we advertise it as working, try codeblocks --help :)
--- End quote ---
using CB from within CI is great and powerfull, no need for makefiles, the console branch for that matter, and when the next step is there that it can also run plugins, then you could have a target that runs a valgrind sessions, a cppcheck, a doxygen, and so on ...
MortenMacFly:
--- Quote from: oBFusCATed on September 02, 2012, 05:01:34 pm ---Because we advertise it as working, try codeblocks --help :)
--- End quote ---
Yes, but we don't advertise its working w/o UI. And batch build is working just great - I do it nearly every day. Its really fast and has a lot advantages in contrast to Makefiles. What I meant is if you really need a build w/o UI you could do it with the Makefile generator. Jens did a trial in the console branch - this could be a starter for what I had in mind (or maybe a solution already).
I know it would be nice to have the build system decoupled - but I think the effort of re-factoring the whole SDK - especially removing all UI parts to achieve this - is just too much if there are other way easier possibilities. Just my 2 cents...
oBFusCATed:
--- Quote from: MortenMacFly on September 03, 2012, 09:02:26 am ---Yes, but we don't advertise its working w/o UI. And batch build is working just great - I do it nearly every day. Its really fast and has a lot advantages in contrast to Makefiles. What I meant is if you really need a build w/o UI you could do it with the Makefile generator. Jens did a trial in the console branch - this could be a starter for what I had in mind (or maybe a solution already).
--- End quote ---
Yes, but you're a windows user and the ui is built-in. On linux you can have pure systems without ui, there it is not working.
--- Quote from: MortenMacFly on September 03, 2012, 09:02:26 am ---I know it would be nice to have the build system decoupled - but I think the effort of re-factoring the whole SDK - especially removing all UI parts to achieve this - is just too much if there are other way easier possibilities. Just my 2 cents...
--- End quote ---
We will see in the future. Anyway having less gui in the SDK will always be good.
MortenMacFly:
--- Quote from: oBFusCATed on September 03, 2012, 09:42:45 am ---Yes, but you're a windows user and the ui is built-in. On linux you can have pure systems without ui, there it is not working.
--- End quote ---
I know, but the batch build feature was never intended to be used without UI, just for batching C::B in a UI capable environment.
However - I indeed have a question: I don't use Linux regularly as you know - so what is the use-case actually that you need to compile projects on a OS without UI? From my limited point of view it only makes sense to compile console projects under such OS'es as everything else won't work. And this works just fine with a Makefile export. Why would you want to compile more complex projects (i.e. UI capable ones) on such OS'es where you cannot test what you've compiled and need a UI capable OS then anyways? ??? This isn't clear to me.
Jenna:
It's very useful for build-robots for example.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version