Did the Adobe Flex SDKs ship like this or were there Mac and Win versions? -Alex
On 5/13/14 1:26 AM, "Christofer Dutz" <[email protected]> wrote: >Would also like something like this ... this way the mavenizer could >mavenize all runtimes in one pass :-) > >Chris > >________________________________________ >Von: Mihai Chira <[email protected]> >Gesendet: Dienstag, 13. Mai 2014 00:44 >An: [email protected] >Betreff: Re: How to merge Windows and Mac SDKs > >(re-sending this as it didn't reach the list on the first attempt) > > >On 9 May 2014 16:49, Mihai Chira <[email protected]> wrote: > >> Our team has both Win and Mac developers, so the SDK needs to support >>both >> setups. I'm very curious how other teams do it, and if there is a >>suggested >> way to merge the SDKs. >> >> Until now we simply downloaded the Flex and AIR SDKs using the >>installers >> for mac and windows, then copied a few key folders and files[1] from the >> mac to the windows version, and it worked. >> >> With v4.12.1, however, the Mac FlashBuilder builds the application >> successfully, but cannot launch it. The error message is "Process >> terminated without establishing connection to debugger." This is >>displayed >> immediately, not after the infamous 57% hangup. >> >> Faced with this, we copied everything that existed in the mac sdk but >>not >> in the windows SDK to the final SDK folder. This did not help either. >> >> From the above I hypothesise that adl depends on some files which exist >>in >> both SDKs, yet are different in each. Can anyone confirm or contradict >>this? >> >> Any help is warmly appreciated. >> >> >> >> >> PS: before trying these debugging steps[2] we thought we'd ask how other >> people do it, in case it's very different. Also because they'd take us >> long, as we're new to OS X. >> >> [1] bin/adl; runtimes/air-captive/mac; and runtimes/air/mac >> [2] https://forums.adobe.com/thread/864473 >>
