I'm not sure whether it is even matter what version we have in case where
we have SDK for pure JS development. For sure we cannot have specify in
"library-path" and "external-library-path" paths to player.
Piotr
2017-09-04 8:38 GMT+02:00 Alex Harui :
> OK. That's what
OK. That's what I hoped. So the goal should be for the installer to set
target-player to something like 11.1?
Thanks,
-Alex
On 9/3/17, 11:19 PM, "Piotr Zarzycki" wrote:
>Once I get back "target-player" to flex-config, but still left commented
>out
Once I get back "target-player" to flex-config, but still left commented
out external-library-path and library-path everything has build without the
problem.
Piotr
2017-09-04 2:18 GMT+02:00 Alex Harui :
> OK, but if you specify a legitimate target-player but only
OK, but if you specify a legitimate target-player but only specify JSFlex
output, I'm still wondering what part of the compiler is going to verify a
playerglobal.swc exists since playerglobal.swc shouldn’t be specified in
any external-library-path.
-Alex
On 9/3/17, 1:51 PM, "Piotr Zarzycki"
Hi Alex,
I get back to this and look closer into compiler code regarding point #1. I
see following comments in Configuration.java:
"The major_version is required while minor_version and revision are
optional. The minimum value is 10.0.0. If you do not specify the
minor_version or revision, then
Alex,
Thank you very much for your reply.
It seems that problem was JAVA_HOME variable. After setting this variable
installation completed successfully.
Regards
--
View this message in context:
Bonjour,
En congés jusqu'au 4 septembre, je prendrais connaissance de votre message à
mon retour.
Cordialement,
Vincent/AFTER24
Hmm. It isn't obvious to me:
1) if you only have target=JSFlex, why does the compiler care about
target-player?
2) Why did -htmlTemplate option not work?
Maybe the console output would tell us more, or try putting
System.out.println calls into MXMLFlexJSPublisher.java to see why the
template
Hi Alex,
I just did build using console. It look like there is a bug in Moonshine
partially.
Build in Moonshine:
Basically when I run build it has failed with same error in Moonshine, cause
every build generates custom configuration [1] which contains
0.0.0 - if there is no player version in
Hi Piotr,
You might have to change more than that in installer.xml. I think there
are other places that fix up flex-sdk-description.xml.
Also, try compiling from the command-line to see what the compiler expects
vs the IDE.
HTH,
-Alex
On 8/28/17, 12:03 PM, "piotrz"
Additionally I just did small experiment making following things:
1) I downloaded nightly build of FlexJS from jenkins
2) Removed from installer.xml "ask-air,ask-flash" and change properties
falcon.version to 0.9.0
3) I tried build simple project using Moonshine and got errors [1]
4) I've
I just thought to check the log to see what the next step is after
uncompressing. On Windows, the install script tries to find JAVA_HOME and
verify that it points to a java executable. Could it be that you don't
have Java installed or a way to find it? Try running from a command
prompt:
Hi Josh,
I think that would a good change if you could do this.
I just tried installer.xml file and it asked for Adobe Air - failed when I
choose "n". - If we could change it for non required.
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
VSCode checks if an SDK contains two directories named "bin" and
"frameworks", and it requires either "flex-sdk-description.xml" or
"air-sdk-description.xml" in the root of the SDK.
One change that I could make is to allow "bin" to be missing if "js/bin"
exists instead.
The parts of Moonshine
AIR and Flash are already technically prerequisites, but folks found it so
inconvenient compared to the old Adobe distributions that Om and others
created the Installer to automate fetching the Flash/AIR bits.
Flash Builder, and maybe some other IDEs, expect AIR and Flash files in
the SDK folder.
I just tried it and it worked for me.
Do you have any restricted access rights to parts of your file system? I
thought we'd gotten rid of "spaces in path" bugs, but maybe try installing
to a folder without spaces in it.
Thanks,
-Alex
On 8/28/17, 4:10 AM, "m_awais" wrote:
Hmm... if we just would like to target JS, do we still need AIR and
playerglobal.swc?
If not, maybe we could provide a FlexJS "JS only" version?
Maybe another approach could be to declare AIR as a prerequisite?
Thanks,
Olaf
--
View this message in context:
I doubt that we can hold somewhere on the Apache server Adobe Air SDK or
playerglobal.swc.
That is why installer was created I think.
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
Hi,
is there any chance to pre-build the various FlexJS releases including the
nightly (maybe also for different platforms) at server side in order to just
provide an URL to make it downloadable?
So the question is, could we replace the installer by manual SDK downloads
for FlexJS?
And if not, is
Om,
Can we install using npm also nightly build (0.9.0) ?
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Flex-JS-Flex-SDK-Installer-always-get-stuck-at-Finish-uncompressing-tp63989p63991.html
Hi,
I haven't tried it, but anyone from PMC know whether we can install FlexJS
by ant script ?
As for the issue - if script doesn't work for you - You can try to install
FlexJS using npm [1]
[1] https://www.npmjs.com/package/flexjs
Thanks,
Piotr
-
Apache Flex PMC
21 matches
Mail list logo