User forums > Using Code::Blocks

commandline build with no gui

<< < (2/3) > >>

rickg22:
I've been doing experiments with my video editing project, and I've found a successful way to make an app which does not actually start up the wxWidgets GUI.

http://svn.berlios.de/svnroot/repos/saya/trunk/src/ui/app.cpp
http://svn.berlios.de/svnroot/repos/saya/trunk/src/main.cpp

The trick is using the unpopular wxEntryStart and wxEntryCleanup() functions (of course, if you don't have a wxApp, you won't be able to rely on the wxWidgets event handling, which is the tricky part). Once you make an application object that is not a subclass of wxApplication, everything is smooth.

I've also been successful at making an independent but wxWidgets compatible string
(see http://svn.berlios.de/svnroot/repos/saya/trunk/src/saya/core/systring.h and
http://svn.berlios.de/svnroot/repos/saya/trunk/src/saya/core/systring.cpp ). This was because I was asked to port the application to QT, so I'm making a combination of replacement / wrapper classes in the ui directory. This has given me A LOT of control over my application's features.

Just in case you wanted to start working on the "commandline codeblocks" project again.

steedhorse:
In my opinion, although it might be hard to implement, it is a very important feature that we can build project or workspace from raw character console device.
Otherwise, we often have to use other tools, such as automake to set up another set of configurations to be used in daily build server.
But I have get used to get everything done in C::B: define projects dependencies, define and use variables, set up pre-build and post-build steps, configure include and lib paths....... It's a misery to repeats all these using automake.:-(

If the using of wx of current C::B makes it hard to accomplish this, I think at least we can set up another separated small sub-project, using no wxWidget stuffs, just a console app that parse .cbp or .workspace files, extracting all configurations, and then do what should be done accordingly.
I really need this feature.:(

stahta01:

--- Quote from: steedhorse on December 22, 2008, 07:12:41 am ---If the using of wx of current C::B makes it hard to accomplish this, I think at least we can set up another separated small sub-project, using no wxWidget stuffs, just a console app that parse .cbp or .workspace files, extracting all configurations, and then do what should be done accordingly.
I really need this feature.:(

--- End quote ---

I was just wondering what plug-ins do you think should be able to work with an command-line only Code::Blocks?
Compiler is needed, but the others are questionable.

Tim S

grischka:
I've once made a small commandline tool ("cbp2mak") that converts codeblocks projectfiles (.cbp) and workspace files (.workspace) to makefiles for mingw.

It's probably far from being complete but it works for the codeblocks project itself.  It's only tested with mingw, porting it might need some work.

Anyway, code is attached. See readme.txt for details.

Regards


[attachment deleted by admin]

kgb98egr:
grischka,

I am new to codeblocks and am trying to use it as the IDE for our developers who work on code that has automatic nightly builds.  Your tool cbp2mak could be useful.  Could I get a copy of your code and readme.txt?

In your last post you say code is attached, but I don't see how to get it.

Thanks

Navigation

[0] Message Index

[#] Next page

[*] Previous page