Well it looks like this is the case. Hahaha @Harb, feeling bad is "my natural state" since a couple of years ago, hahahaha, but thanks for the encouragement, I appreciate it 😝 and I apologize.
Clarify something for me,.... The prevent-rename* options why don't they make sense in a bookstore? There are public classes in them that may not have to be renamed, right? Tell me what I'm missing, hahahaha, I'll make a fool of myself again. Hiedra -----Mensaje original----- De: Josh Tynjala <joshtynj...@bowlerhat.dev> Enviado el: lunes, 3 de enero de 2022 21:23 Para: dev@royale.apache.org Asunto: Re: command line unknown configuration variable 'prevent-rename-public-symbols' The prevent-rename-* options are used only when compiling a release build of an application. They are not used when compiling libraries, so the library compiler compc does not make them available. With that in mind, the error is normal and expected, and you can remove prevent-rename-* from your library's additional options. Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> On Mon, Jan 3, 2022 at 11:47 AM Maria Jose Esteve <mjest...@iest.com> wrote: > I sent the message without finishing... > > I forgot to comment a detail that must be important... > The error only occurs when compiling the library. I have this same > option in the pom of the application and there it does recognize it... > Why can it be? Why can it be, because of the type of packaging swf/swc? > > Hiedra > > -----Mensaje original----- > De: Maria Jose Esteve <mjest...@iest.com> Enviado el: lunes, 3 de > enero de 2022 20:36 > Para: dev@royale.apache.org > Asunto: RE: command line unknown configuration variable > 'prevent-rename-public-symbols' > > Same result, ☹ > > Hiedra > > -----Mensaje original----- > De: Maria Jose Esteve <mjest...@iest.com> Enviado el: lunes, 3 de > enero de 2022 19:58 > Para: dev@royale.apache.org > Asunto: RE: command line unknown configuration variable > 'prevent-rename-public-symbols' > > Hi Josh, on this machine I only have sdk 0.9.9. Anyway, I have > rebooted the machine, and compiled the SDK just now and the result is > unchanged. > Although I know it's silly, I went to check the compiler code and the > option exists. > Last night it didn't give me these errors... I'll compile it again. > > Hiedra > > -----Mensaje original----- > De: Josh Tynjala <joshtynj...@bowlerhat.dev> Enviado el: lunes, 3 de > enero de 2022 18:39 > Para: dev@royale.apache.org > Asunto: Re: command line unknown configuration variable > 'prevent-rename-public-symbols' > > If I had to guess, it probably means that you are compiling with an > older version of Royale that did not yet have this compiler option. > > -- > Josh Tynjala > Bowler Hat LLC <https://bowlerhat.dev> > > > On Mon, Jan 3, 2022 at 4:50 AM Maria Jose Esteve <mjest...@iest.com> > wrote: > > > Hello, does anyone know why I get this message when compiling? > > "command line unknown configuration variable > > 'prevent-rename-public-symbols'" > > > > -js-default-initializers=true > > -js-dynamic-access-unknown-members=true > > -source-map=true > > > > -source-map-source-root=D:\Develop_Royale\Projects\WinPlusWebSuite\r > > oy alelibs\royalesecurity/src/main/royale/ > > > > -keep-as3-metadata+=Inject,Dispatcher,EventHandler,Event,PostConstru > > -keep-as3-metadata+ct > > -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transi > > -keep-as3-metadata+en > > -keep-as3-metadata+t > > -keep-code-with-metadata=Inject > > -show-binding-warnings=false > > -export-public-symbols=true > > -prevent-rename-public-symbols=true > > -export-protected-symbols=true > > -export-internal-symbols=true > > -compiler.targets=SWF,JSRoyale > > -compiler.strict-xml=true > > command line unknown configuration variable > > 'prevent-rename-public-symbols'. > > > > Thx > > > > Hiedra > > > > >
