Creating Mac standalone on Windows Studio?

[Steve King]

Hi All

I know nothing at all of Macs....

I have Rev Studio (windows) and in the standalone builder there is a Mac
(OSX) tab and when I build my Windows Standalone, I also get a Mac folder.

Is this a Mac standlone of any type? If so, how is it used. What is OSX?

I never build for Macs, it just happens in the club this application is for
there is one Mac user. All the rest are windows users.

Cheers
Steve

[Paul D. DeRocco]

From: Steve King
I know nothing at all of Macs....
I have Rev Studio (windows) and in the standalone builder there is a Mac
(OSX) tab and when I build my Windows Standalone, I also get a Mac folder.
Is this a Mac standlone of any type? If so, how is it used. What is OSX?
I never build for Macs, it just happens in the club this
application is for
there is one Mac user. All the rest are windows users.

Yes, if you checked the box telling it to build an OS-X standalone too.
Under the Mac folder, there should be a .app folder, which is the Mac
application.

--

Ciao, Paul D. DeRocco
Paul mailto:***@ix.netcom.com

[Richard Gaskin]

Post by Steve King
I know nothing at all of Macs....
I have Rev Studio (windows) and in the standalone builder there is a Mac
(OSX) tab and when I build my Windows Standalone, I also get a Mac folder.
Is this a Mac standlone of any type? If so, how is it used. What is OSX?

"OSX" is a misspelling of "OS X" ("OS version 10"), the Mac operating
system Apple ships with their computers.

Post by Steve King
I never build for Macs, it just happens in the club this application is for
there is one Mac user. All the rest are windows users.

Unfortunately, Apple's Unix core will require an extra step to deploy there:

The folder you see is what Apple calls a "bundle", and contains all the
parts and pieces the app needs to run, things that are embedded into a
single file on Windows.

Within the bundle at this path:

/<bundlename>.app/Contents/MacOS/<exename>

...where it says <exename> you'll find the actual executable. But since
it was generated from Windows it has no executable bit, which Unix-based
file systems need to run a file as an executable.

To make the app runnnable you'll need to copy the *.app bundle to a Mac,
then on the Mac use Terminal to change the permissions on the executable
using chmod.

If there's an easier way to generate Mac standalones from Windows I
haven't found it.

--
Richard Gaskin
Fourth World
Rev training and consulting: http://www.fourthworld.com
Webzine for Rev developers: http://www.revjournal.com
revJournal blog: http://revjournal.com/blog.irv

[Mark Swindell]

That's seems a ridiculously obtuse process. Not doubting it, but couldn't the application builder be made to take care of this?
Mark

Post by Steve King
I know nothing at all of Macs....
I have Rev Studio (windows) and in the standalone builder there is a Mac
(OSX) tab and when I build my Windows Standalone, I also get a Mac folder.
Is this a Mac standlone of any type? If so, how is it used. What is OSX?

"OSX" is a misspelling of "OS X" ("OS version 10"), the Mac operating system Apple ships with their computers.

Post by Steve King
I never build for Macs, it just happens in the club this application is for
there is one Mac user. All the rest are windows users.

The folder you see is what Apple calls a "bundle", and contains all the parts and pieces the app needs to run, things that are embedded into a single file on Windows.
/<bundlename>.app/Contents/MacOS/<exename>
...where it says <exename> you'll find the actual executable. But since it was generated from Windows it has no executable bit, which Unix-based file systems need to run a file as an executable.
To make the app runnnable you'll need to copy the *.app bundle to a Mac, then on the Mac use Terminal to change the permissions on the executable using chmod.
If there's an easier way to generate Mac standalones from Windows I haven't found it.
--
Richard Gaskin
Fourth World
Rev training and consulting: http://www.fourthworld.com
Webzine for Rev developers: http://www.revjournal.com
revJournal blog: http://revjournal.com/blog.irv
_______________________________________________
use-revolution mailing list
http://lists.runrev.com/mailman/listinfo/use-revolution

[Richard Gaskin]

Post by Mark Swindell
That's seems a ridiculously obtuse process. Not doubting it, but couldn't the application builder be made to take care of this?
Mark

I agree that it's way more work than would be desirable, but we
discussed this here in a thread a couple months back related to a
multi-platform installer I was making and we couldn't come up with a
simpler solution.

The outcome of that thread was that ultimately this is a difference in
file system capabilities, and not something Rev can address. You simply
can't set the Unix executable bit from Windows, since the Win file
system has no such property.

If someone comes up with a way to do it I'd be very happy to learn it,
but last time we explored it here we came up empty.

--
Richard Gaskin
Fourth World
Rev training and consulting: http://www.fourthworld.com
Webzine for Rev developers: http://www.revjournal.com
revJournal blog: http://revjournal.com/blog.irv

Post by Mark Swindell

Post by Steve King
I know nothing at all of Macs....
I have Rev Studio (windows) and in the standalone builder there is a Mac
(OSX) tab and when I build my Windows Standalone, I also get a Mac folder.
Is this a Mac standlone of any type? If so, how is it used. What is OSX?

"OSX" is a misspelling of "OS X" ("OS version 10"), the Mac operating system Apple ships with their computers.

Post by Steve King
I never build for Macs, it just happens in the club this application is for
there is one Mac user. All the rest are windows users.

The folder you see is what Apple calls a "bundle", and contains all the parts and pieces the app needs to run, things that are embedded into a single file on Windows.
/<bundlename>.app/Contents/MacOS/<exename>
...where it says <exename> you'll find the actual executable. But since it was generated from Windows it has no executable bit, which Unix-based file systems need to run a file as an executable.
To make the app runnnable you'll need to copy the *.app bundle to a Mac, then on the Mac use Terminal to change the permissions on the executable using chmod.
If there's an easier way to generate Mac standalones from Windows I haven't found it.

[Mark Swindell]

Quite the conundrum. Thanks for the explanation. New motto: Write once, wrestle lots, and deploy on multiple platforms.

Mark

Post by Mark Swindell
That's seems a ridiculously obtuse process. Not doubting it, but couldn't the application builder be made to take care of this?
Mark

I agree that it's way more work than would be desirable, but we discussed this here in a thread a couple months back related to a multi-platform installer I was making and we couldn't come up with a simpler solution.
The outcome of that thread was that ultimately this is a difference in file system capabilities, and not something Rev can address. You simply can't set the Unix executable bit from Windows, since the Win file system has no such property.
If someone comes up with a way to do it I'd be very happy to learn it, but last time we explored it here we came up empty.
--
Richard Gaskin
Fourth World
Rev training and consulting: http://www.fourthworld.com
Webzine for Rev developers: http://www.revjournal.com
revJournal blog: http://revjournal.com/blog.irv

Post by Mark Swindell

Post by Steve King
I know nothing at all of Macs....
I have Rev Studio (windows) and in the standalone builder there is a Mac
(OSX) tab and when I build my Windows Standalone, I also get a Mac folder.
Is this a Mac standlone of any type? If so, how is it used. What is OSX?

"OSX" is a misspelling of "OS X" ("OS version 10"), the Mac operating system Apple ships with their computers.

Post by Steve King
I never build for Macs, it just happens in the club this application is for
there is one Mac user. All the rest are windows users.

The folder you see is what Apple calls a "bundle", and contains all the parts and pieces the app needs to run, things that are embedded into a single file on Windows.
/<bundlename>.app/Contents/MacOS/<exename>
...where it says <exename> you'll find the actual executable. But since it was generated from Windows it has no executable bit, which Unix-based file systems need to run a file as an executable.
To make the app runnnable you'll need to copy the *.app bundle to a Mac, then on the Mac use Terminal to change the permissions on the executable using chmod.
If there's an easier way to generate Mac standalones from Windows I haven't found it.

_______________________________________________
use-revolution mailing list
http://lists.runrev.com/mailman/listinfo/use-revolution

[J. Landman Gay]

Post by Mark Swindell
Quite the conundrum. Thanks for the explanation. New motto: Write
once, wrestle lots, and deploy on multiple platforms.

To be fair, it's easy and as advertised to build on all platforms from
any OS, with this one exception of building for OS X from Windows. You
can't really blame Rev for not being able to support something that
Windows isn't capable of doing. Windows is completely unaware of any
unix-based permissions. Going the other direction -- building on other
platforms for Windows deployment -- works fine and as expected.

[Mark Swindell]

I meant to be more silly than sarcastic. :)

It works fine the way I use it, from Mac to Windows. But it can't be denied it's not so simple if you write on Windows and wish to deploy on Mac, and that is sort of 1/2 of the common equation for x-platform deployment, isn't it?

Mark (Not meaning to offend the Linux folks, but Windows and Mac are still the main supported platforms from all I read here.)

Post by Mark Swindell
Quite the conundrum. Thanks for the explanation. New motto: Write
once, wrestle lots, and deploy on multiple platforms.

To be fair, it's easy and as advertised to build on all platforms from any OS, with this one exception of building for OS X from Windows. You can't really blame Rev for not being able to support something that Windows isn't capable of doing. Windows is completely unaware of any unix-based permissions. Going the other direction -- building on other platforms for Windows deployment -- works fine and as expected.
--
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
http://lists.runrev.com/mailman/listinfo/use-revolution

[Bob Sneidar]

On Windows, you make something executable by putting .exe at the end. Of course, if it's not a real executable, nothing will happen, and if it is a real executable, and you don't put .exe at the end, it won't execute. This actually makes it a simple matter to send someone what looks like a jpg file, but with .exe at the end, and because Windows is hiding known extensions by default, (I know you can change that) you can trick a user into double clicking it and executing malicious code. Not so simple for a unix/linux based system. If the executable bit is in the file itself, Rev for Windows should be able to set it, but if it's some hidden system file somewhere, like an acl, then there is no real way to do it methinks.

Bob

Post by Mark Swindell
Quite the conundrum. Thanks for the explanation. New motto: Write
once, wrestle lots, and deploy on multiple platforms.

To be fair, it's easy and as advertised to build on all platforms from any OS, with this one exception of building for OS X from Windows. You can't really blame Rev for not being able to support something that Windows isn't capable of doing. Windows is completely unaware of any unix-based permissions. Going the other direction -- building on other platforms for Windows deployment -- works fine and as expected.
--
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
http://lists.runrev.com/mailman/listinfo/use-revolution

[Peter Alcibiades]

Dioes the Finder have the ability to get and set properties, ie permissions?
The usual thing to do in Linux, very similar base, would be to tell the user
to right click in a file manager, ie in the Mac case the Finder, get
properties, and change the permissions to executable. You wouldn't normally
need to ask them to do that in the terminal. Haven't used Macs for quite a
while, so maybe it doesn't work like this.

[J. Landman Gay]

Post by Peter Alcibiades
Dioes the Finder have the ability to get and set properties, ie permissions?
The usual thing to do in Linux, very similar base, would be to tell the user
to right click in a file manager, ie in the Mac case the Finder, get
properties, and change the permissions to executable. You wouldn't normally
need to ask them to do that in the terminal. Haven't used Macs for quite a
while, so maybe it doesn't work like this.

The Finder can set user permissions for the user, group, and everyone.
But it doesn't have an interface for the executable bit, that has to be
done in Terminal. Perhaps Apple didn't think the executable bit should
be messed with by the peons -- probably wise, considering the computer
savvy of the general population.

[stephen barncard]

Jacque: By "done in the terminal" does that mean it can't be done by shell()
?

Post by Peter Alcibiades
Dioes the Finder have the ability to get and set properties, ie
permissions? The usual thing to do in Linux, very similar base, would be to
tell the user
to right click in a file manager, ie in the Mac case the Finder, get
properties, and change the permissions to executable. You wouldn't normally
need to ask them to do that in the terminal. Haven't used Macs for quite a
while, so maybe it doesn't work like this.

The Finder can set user permissions for the user, group, and everyone. But
it doesn't have an interface for the executable bit, that has to be done in
Terminal. Perhaps Apple didn't think the executable bit should be messed
with by the peons -- probably wise, considering the computer savvy of the
general population.
--
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
Please visit this url to subscribe, unsubscribe and manage your
http://lists.runrev.com/mailman/listinfo/use-revolution

[J. Landman Gay]

Post by stephen barncard
Jacque: By "done in the terminal" does that mean it can't be done by shell()
?

Oh no, you can do anything in shell that you can do in Terminal. "Done
in Terminal" is my personal, all-inclusive term for the command line. :)

[Bob Sneidar]

I believe in Leopard or Snow Leopard they support ACL's as well. Now if we can only get Apple to make their ACL's implicitly inherited as in Windows for the clients as well as the server software, we will be saying something! But that's another thread.

Bob

Post by J. Landman Gay
The Finder can set user permissions for the user, group, and everyone.

[Peter Alcibiades]

OK, then you have to write a shell script.

Get the root password by asking for it on installation..

Then go out to shell and call a script which will switch user to root, give
the password, then set the executable bit. I don't know OSX, but this
should be pretty simple to do in any unix.

[Francis Nugent Dixon]

Hi from Beautiful Brittany,

Post by Steve King
I know nothing at all of Macs....

Steve, my heart bleeds for you - ..... and you are so, so many !

But you are in the right forum to ask questions, and to find
the true road to salvation ..... :>)

-Francis