Hello, I understand, Greg, that all artifacts using crux should have the same value of -keep-as3-metadata right?....
I have spent much of today investigating this bug and I don't know where to continue. I don't know why since I compiled the SDK yesterday my main project has broken, as I commented in my first post (I compile the project successfully but when it initializes it gives error one of the Injects used in a controller). As I have another pc, "without yesterday's compilation" I have compared the sdk directories and except for the normal differences due to code update, the rest I see it the same. Other tests: - I have compiled, on my main machine, the sdk (asjs, compiler and typedefs) at the same point I have the other machine and it doesn't work either. - I have deleted from the HD the 3 repos; I have re-downloaded them from github, and I have compiled as of 13.12.2020, without success either. - I deleted the ".m2/.../royale" directory before any testing, and the ".m2/com/...my project" directory as well to be sure I didn't catch anything new or old. - I have compiled only JS, with SWF, ... nothing worked for me. But my main concern is to understand why from the compilation I did on the 13 to the compilation I did on the 14 this has occurred. I thought maybe it would be caused by Josh's changes to royale-compiler but when I compile to an earlier date it doesn't work either, so it must not be that. What could be catching the compile incorrectly so that it doesn't find me, nor in debug, "some classes" that I have in my library? Thoughts? Thanks. Hiedra -----Mensaje original----- De: Greg Dove <greg.d...@gmail.com> Enviado el: jueves, 16 de diciembre de 2021 10:28 Para: Apache Royale Development <dev@royale.apache.org> Asunto: Re: Error crux InjectProcessor/setUpMetadataTag > In any case... you didn't talk about -keep-as3-metadata or -keep-code-with-metadata but about the "rename" options... what do these two options indicate? I didn't talk about the prevent-rename options (I have not used these options yet), I think that was Harbs and/or Josh. -keep-as3-metadata makes sure you keep all the metadata that is useful/required for Crux to work or -keep-code-with-metadata is another option that I think Alex added at one point which (I think) had some protection from dead-code-elimination, but perhaps that has changed now is not needed. On Thu, Dec 16, 2021 at 10:06 PM Maria Jose Esteve <mjest...@iest.com> wrote: > Hi Greg, thanks for replying > No, the tests with the optional compile parameters I have them in > another branch. > In any case... you didn't talk about -keep-as3-metadata or > -keep-code-with-metadata but about the "rename" options... what do > these two options indicate? > > > If you have an archived version of the full js build that worked, > > you > could maybe do some sort of diff of the build fileset to look for > major changes. > > Yes, I have another machine with a build from a week ago. I have > tested on that machine the project and I have no problems, it runs > perfectly in debug (in release I have the same minification errors we talked > about days ago). > My current build is "no distribution", I'm going to follow your > suggestion and compare them to see if I see anything. > I'm also going to try to delete the .m2 royale folder in case it > "rings the bell" 😝. > > I'll tell you now. > > Hiedra > > -----Mensaje original----- > De: Greg Dove <greg.d...@gmail.com> > Enviado el: jueves, 16 de diciembre de 2021 9:40 > Para: Apache Royale Development <dev@royale.apache.org> > Asunto: Re: Error crux InjectProcessor/setUpMetadataTag > > Hi Maria, > > It's really difficult to say. > Maybe you did a full clean and removed some cached js files for > library swcs that have since changed. > If you have an archived version of the full js build that worked, you > could maybe do some sort of diff of the build fileset to look for > major changes. > > You definitely didn't change the settings for -keep-as3-metadata or > -keep-code-with-metadata, right? (I think you already said no, but I > am just double checking, because I have done things like this before > myself) > > > > > > > On Thu, Dec 16, 2021 at 3:04 PM Maria Jose Esteve <mjest...@iest.com> > wrote: > > > Hi, I need your help... > > I downloaded and compiled the SDK and my project "crashed" ☹ an > > error occurs on initialization [1]. > > Yesterday, I downloaded and compiled the SDK and everything was working. > > > > I just compiled the SDK at the same point I compiled it yesterday > > BUT now I am NOT getting the project to work, how can this happen, > > is it picking up some incorrect, or pre-cached reference? > > > > As this week we have been talking about compiler options and > > problems with releases, etc, etc, I must clarify that I have not > > made any modifications to this branch of the project. > > Any help would be welcome. > > > > [1] > > https://drive.google.com/file/d/1RSrhlnSzxtjnN00-c6GxSFPJBNDkgGcx/vi > > ew > > ?usp=sharing > > > > Thx. > > Hiedra > > > > > > > > >
