Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

SDK refactoring for non UI builds

<< < (2/5) > >>

oBFusCATed:

--- Quote from: MortenMacFly on September 02, 2012, 04:06:14 pm ---For such it would be nice if you could simple derive from the existing class and change what's needed.

--- End quote ---
For a class to be derivable, it should be designed with this in mind and I doubt this is the case for most of them.


--- Quote from: MortenMacFly on September 02, 2012, 04:06:14 pm ---I wonder what's so bad about it.

--- End quote ---
Because we can't have a console-only executable on linux, which can be used for building cb projects.


--- Quote from: MortenMacFly on September 02, 2012, 04:07:39 pm ---...reminds me on something else I noticed with the ThreadSearch dialog: I regularly become warnings that ThreadSearch tries to find in binary files, like icons. This is rather annoying and makes me use the "normal" find dialog more often.

--- End quote ---
Fix your file mask and you won't get such problems.

MortenMacFly:

--- Quote from: oBFusCATed on September 02, 2012, 04:12:21 pm ---Because we can't have a console-only executable on linux, which can be used for building cb projects.

--- End quote ---
I think a more clever way would be to re-factor the build system and compiler plugin so it offers a way to be bundled into a console version. You don't need any UI/other plugin if you want to compile from console.


--- Quote from: oBFusCATed on September 02, 2012, 04:12:21 pm ---Fix your file mask and you won't get such problems.

--- End quote ---
My file mask is: "*.cpp;*.c;*.h". Something else is wrong - it might be related that I search the whole workspace. It seem to happen only then.

Edit: Concerning: "You don't need any UI/other plugin if you want to compile from console" - maybe you do: the EnvVars plugin.

MortenMacFly:

--- Quote from: MortenMacFly on September 02, 2012, 04:21:07 pm ---I think a more clever way would be to re-factor the build system and compiler plugin

--- End quote ---
BTW: What I did in one of my own applications that is similar:
- all classes accessing files are based on non-GUI components (and are also part of a SDK)
- for the UI version of the software I have a gateway class that "connects" low-level stuff to high-level UI events/commands.
- for the non-UI version I use this specific part of the SDK decoupled and wrapped with a command line interface around it.
In a similar fashion the build system could be designed.

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?

oBFusCATed:

--- 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  :)

Jenna:

--- Quote from: MortenMacFly on September 02, 2012, 04:21:07 pm ---
--- Quote from: oBFusCATed on September 02, 2012, 04:12:21 pm ---Because we can't have a console-only executable on linux, which can be used for building cb projects.

--- End quote ---
I think a more clever way would be to re-factor the build system and compiler plugin so it offers a way to be bundled into a console version. You don't need any UI/other plugin if you want to compile from console.


--- Quote from: oBFusCATed on September 02, 2012, 04:12:21 pm ---Fix your file mask and you won't get such problems.

--- End quote ---
My file mask is: "*.cpp;*.c;*.h". Something else is wrong - it might be related that I search the whole workspace. It seem to happen only then.

--- End quote ---
As far as I know, the filemask is not used in this case, all project/workspace files are used.
The filemask is only used when searching in a given directory.

EDIT:
That's why the possibility to ignore some errors was added in the config-dialog, we might add one to ignore e.g. binary file-errors.
This should be easy to implement. I can do this.


--- Quote from: MortenMacFly on September 02, 2012, 04:21:07 pm ---Edit: Concerning: "You don't need any UI/other plugin if you want to compile from console" - maybe you do: the EnvVars plugin.

--- End quote ---
In this case a user should either use cb_share_config to export the envvars or set the needed vars in a shell-script and run C::B from inside it.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version