Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Community » U++ community news and announcements » ide: main.conf
Re: ide: main.conf [message #40714 is a reply to message #40713] Sun, 08 September 2013 11:04 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 14265
Registered: November 2005
Ultimate Member
dolik.rce wrote on Sun, 08 September 2013 04:10

mirek wrote on Mon, 26 August 2013 13:57

New feature of ide (and umk) build system:

All files named "main.conf" from all packages are appended together (in unspecified order), result placed on output directory of main package into main.conf.h file (always, even if it is empty). Path to this directory is placed to the include set. Ide/umk supporting this feature defines MAIN_CONF macro.

Hi Mirek

This will make it a bit harder again to use U++ sources without TheIDE (or umk). As I try to maintain the universal makefile fully compatible with TheIDE, this is not really a good news for me Wink So I have few questions:



I understand that. I think that theide will always be possible to build without this feature.

Quote:


Do you plan to use this in any of the core packages soon? I've found no mention of this in svn so far.

Will it always be guarded by #ifdef MAIN_CONF for backwards compatibility? Or at least for some period of time, to allow transition to newer build system (be it TheIDE or makefile)?



I plan to something like

#ifdef MAIN_CONF
#include "main.conf.h"
#endif

into Core/Core.h soon - and that is about it, nothing else is ever required... Which means that for now, no changes are required as well.

Quote:


Wouldn't it be better to use existing "Add/Remove flags" functionality of Package manager for this? To use your example, the package that wants to include it own font handling could just have "flags CUSTOM_FONTSYS;" in .upp file and Draw package would then turn off the generic font handling based on #ifdef flagCUSTOM_FONTSYS. I'm aware that main.conf as you designed it will allow much more than this, but I'm not sure if it is really necessary.



I do not really see a difference with breaking stuff one way or another... Smile

Add/remove packages work for package compiled and do not allow to define values. I can sure invent some new "Add/remove global flags", but I really am not sure how would that improve the situation.... Build system has to be adjusted anyway and it should be no harder to implement main.conf than new flags, I think...

All that said, main.conf is right now just experimental attempt to solve given issue. I might be possible that we will find another solution to this...

Mirek
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: New small hidden feature of ArrayCtrl
Next Topic: *Maps syntax sugar
Goto Forum:
  


Current Time: Tue Jul 08 10:15:21 CEST 2025

Total time taken to generate the page: 0.04073 seconds