Re: [qooxdoo-devel] Compilation issue
Brought to you by:
ecker,
martinwittemann
From: thron7 <tho...@1u...> - 2013-06-28 21:00:17
|
> I'm using the 2.1.1 This issue has been taken care of long ago, and hasn't come up in a long time. Unless you discovered a tricky regression there must be something specific in your setup. For one thing, the affected Generator step is the private optimization, and hence the natural work-around is to disable "privates" in the optimization settings. Private optimization needs "perfect knowledge" to work, i.e. the Generator needs to know *all* classes that go into the build, in order to perform this optimization correctly. For each class it maintains a list of privates and their replacements. If a new class is compiled into the build this index is used to make sure that no replacement string is used twice. The index itself is kept in the cache directory (in a file named "privates") so it can be used with every build run consistently, even though some classes might have been already compiled. When the cache is cleared everything has to be calculated anew, so also the "privates" index is rebuild. The way to trick this system is to somehow modify the privates index independent from the class compilation. This can be achieved by splitting up the set of classes that go into the application, and compile them independently, e.g. with two different caches or by deleting the "privates" file from the cache without clearing the compiled class code. - Do you do anything of that kind? T. > > > 2013/6/28 thron7 <tho...@1u...> > >> This is an issue that is usually dealt with. Which qooxdoo version are >> you using? >> >> T. >> >> >> >> On 06/28/2013 03:49 PM, Benjamin Dreux wrote: >> >> Hi >> >> I'm having an issue that can occures somethings with the compiled >> version of my app. >> Sometimes private members overrides each other. >> >> Here is my class >> http://pastebin.com/gXrdMnRE >> My i don't think it's relevent. >> >> What happens is that the super class have a private member, which end >> up >> being named __bU >> And in my class, i also have a private member that called __createLabel, >> which end up beeing called __bU. >> >> And the issue is that from the derived class point of view, there is >> only one __bU, which is the last one to be defined. >> >> Is this a known issue. Is there a way to fix this for my project and/or >> for qooxdoo ? >> >> Regards >> >> -- >> Benjamin Dreux >> Analyste-Programmeur >> Chaire de logiciel libre-Finance Social et solidaire >> UQAM >> Montréal >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Windows: >> >> Build for Windows Store. >> http://p.sf.net/sfu/windows-dev2dev >> >> >> >> _______________________________________________ >> qooxdoo-devel mailing >> lis...@li...https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >> >> >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Windows: >> >> Build for Windows Store. >> >> http://p.sf.net/sfu/windows-dev2dev >> _______________________________________________ >> qooxdoo-devel mailing list >> qoo...@li... >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >> >> > > > -- > Benjamin Dreux > Analyste-Programmeur > Chaire de logiciel libre-Finance Social et solidaire > UQAM > Montréal > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev_______________________________________________ > qooxdoo-devel mailing list > qoo...@li... > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > |