Runners not launching from command line on Windows

[Ruprict]

Hi,

So, I am trying Sprouts (very excited) and I watched the screencast
and read a bunch of stuff. In my SomeProject, when I run rake, it
builds the swf, but the player never launches nor do I get trace
output at the command line. Same with 'rake test', nothing happens.
I can manually run the test runner, and it runs the tests, but it
doesn't launch from the rake task. I don't get any errors for either
debug or test.

Any idea why that would happen? The install seemed to go as planned.
I am sure I have messed it up somehow.

Thanks,
Ruprict

[Luke Bayes]

Hey Ruprict,

I'm looking into this right now. In the mean time, from your project
folder can you please run the following commands, and send the output
to this list?

ruby -v
gem -v
rake clean
rake


Thanks!

Luke

> --
> You received this message because you are subscribed to the Google Groups "ProjectSprouts" group.
> To post to this group, send email to project...@googlegroups.com
> To unsubscribe from this group, send email to projectsprout...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/projectsprouts?hl=en
>
> For other info you can visit our project at: http://projectsprouts.org, or on Github at: http://github.com/lukebayes/project-sprouts
>

[Luke Bayes]

One more key bit of info...

What version of Windows are you running on?


Thanks,

Luke

[Glenn Goodrich]

Windows 7

From cygwin:

ggoodrich@esi-ggoodrich /cygdrive/c/projects/SomeProject

$ ruby -v

ruby 1.8.7 (2008-08-11 patchlevel 72) [i386-cygwin]

ggoodrich@esi-ggoodrich /cygdrive/c/projects/SomeProject

$ gem -v

1.3.5

ggoodrich@esi-ggoodrich /cygdrive/c/projects/SomeProject

$ rake clean

(in /cygdrive/c/projects/SomeProject)

rm -r bin/SomeProject-debug.swf

rm -r AsUnitResults.xml

rm -r bin/SomeProjectRunner.swf

rm -r AsUnitResults.xml

rm -r bin/SomeProject.swf

rm -r doc

rm -r bin/SomeProject.swc

rm -r bin/SomeProjectXMLRunner.swf

rm -r AsUnitResults.xml

ggoodrich@esi-ggoodrich /cygdrive/c/projects/SomeProject

$ rake

(in /cygdrive/c/projects/SomeProject)

>> Execute: mxmlc.exe -default-background-color=#FFFFFF -default-frame-rate=24 -default-size 970 550 -output=bin/SomeProject-debug.swf -source-path+=src -source-path+=assets -verbose-stacktraces=true -warnings=true src/SomeProject.mxml

Loading configuration file C:\Users\ggoodrich\Local Settings\Application Data\Sprouts\cache\0.7\sprout-flex3sdk-tool-3.3.1\archive\frameworks\flex-config.xml

C:\projects\SomeProject\bin\SomeProject-debug.swf (291960 bytes)

mxmlc finished compiling bin/SomeProject-debug.swf in 15 seconds

ggoodrich@esi-ggoodrich /cygdrive/c/projects/SomeProject

$

From windows cmd:

C:\projects\SomeProject>rake clean

(in C:/projects/SomeProject)

rm -r bin/SomeProject-debug.swf

rm -r AsUnitResults.xml

rm -r bin/SomeProjectRunner.swf

rm -r AsUnitResults.xml

rm -r bin/SomeProject.swf

rm -r doc

rm -r bin/SomeProject.swc

rm -r bin/SomeProjectXMLRunner.swf

rm -r AsUnitResults.xml

C:\projects\SomeProject>rake

(in C:/projects/SomeProject)

>> Execute: mxmlc.exe -default-background-color=#FFFFFF -default-frame-rate=24 -default-size 970 550 -output=bin/SomeProject-debug.swf -source-path+=src -source-path+=assets -verbose-stacktraces=true -warnings=true src/SomeProject.mxml

Loading configuration file C:\Users\ggoodrich\Local Settings\Application Data\Sprouts\cache\0.7\sprout-flex3sdk-tool-3.3.1\archive\frameworks\flex-config.xml

C:\projects\SomeProject\bin\SomeProject-debug.swf (291958 bytes)

mxmlc finished compiling bin/SomeProject-debug.swf in 10 seconds

C:\projects\SomeProject>

Not sure if the dual env is an issue, but hoping that isn't it.

Thanks,

Ruprict

Glenn

gl...@goodrichs.net

[Luke Bayes]

Wow -

That's especially surprising because I could always count on Cygwin to
not be a PITA!

It shouldn't be an issue that you have both environments set up, as we
*should* be storing files and whatnot in different places.

I just re-ran the latest releases on XP, and everything is working
fine here. My biggest suspicion at this point is Windows 7.

To be honest, I haven't even seen Windows 7 at this point, much less
tested Sprouts on it.

So here's the rub. I'm kind of jammed up time-wise until after the big
turkey-day next week.

Would you (or anyone else with access to Windows 7) be interested in
digging into this?

I'm pretty sure you're hitting a problem with the flashplayer_task.rb
that's in the flashplayer-tool gem.

You can open this file directly on your system and add trace
statements to it to find out what's going on, or at least where it's
quitting.

In Ruby, trace is 'puts' and single quotes will emit whatever string
you insert, but double-quotes will render an expression syntax like:

puts ">> FlashPlayer.doingsomething: #{expression}"

Thanks,

Luke

[Glenn Goodrich]

I'll take a stab at it.

--
You received this message because you are subscribed to the Google Groups "ProjectSprouts" group.
To post to this group, send email to project...@googlegroups.com
To unsubscribe from this group, send email to projectsprout...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/projectsprouts?hl=en

For other info you can visit our project at: http://projectsprouts.org, or on Github at: http://github.com/lukebayes/project-sprouts

Glenn

gl...@goodrichs.net

[Luke Bayes]

Running

rake --trace

Can be helpful too...

lb.

[Glenn Goodrich]

Well, that was easy (and stupid on my part...which I expected)

The file wasn't executable...a simple chmod 744, and we're off and running.

Odd that it affected the Windows cmd line tho.  They both work now.

Excellent.

--
You received this message because you are subscribed to the Google Groups "ProjectSprouts" group.
To post to this group, send email to project...@googlegroups.com
To unsubscribe from this group, send email to projectsprout...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/projectsprouts?hl=en

For other info you can visit our project at: http://projectsprouts.org, or on Github at: http://github.com/lukebayes/project-sprouts

Glenn

gl...@goodrichs.net

Glenn

gl...@goodrichs.net

[Luke Bayes]

Sweet!

I disagree that it was your fault, a major point of Sprouts is that it
should "just work". It's frustrating that Adobe packages up
executables without first setting their file mode, but there is some
code in Sprouts that fixes this on other platforms. Since previous
versions of Win didn't care about the file mode, I think we just
ignored it there.

Thanks for figuring it out, and sharing the fix!

Luke