GNU Lesser General Public License gurus or WineHQ contact

Dee Ayy · Post by **Dee Ayy** » Fri Mar 07, 2008 10:40 pm

Did you check out that iPhone SDK keynote? It makes me want to sell software.

Do any of you GNU LGPL gurus understand the license
http://www.winehq.org/site/license to know if we can distribute Wine
to run our MS Windows executable? I'm sure it's something basic (for
a license groker).

I'm not linking with Wine, I just want to install it on the iPhone (if
Apple allows it through their developer programs) and have Wine run my
exe, managed by a Mac OS X app.

Or do you know the WineHQ contact to ask?

Regards.

3vi1 · Post by **3vi1** » Fri Mar 07, 2008 11:15 pm

Doesn't the iPhone use an ARM CPU? How's WINE going to help you there?

vitamin · Post by **vitamin** » Sat Mar 08, 2008 12:12 am

Dee Ayy wrote:Did you check out that iPhone SDK keynote? It makes me want to sell software.

Do any of you GNU LGPL gurus understand the license
http://www.winehq.org/site/license to know if we can distribute Wine
to run our MS Windows executable? I'm sure it's something basic (for
a license groker).

I'm not linking with Wine, I just want to install it on the iPhone (if
Apple allows it through their developer programs) and have Wine run my
exe, managed by a Mac OS X app.

Or do you know the WineHQ contact to ask?

Regards.

You can, as long as you don't modify it. If you do, you have to make all your modifications available to everyone. Up to a point so anyone can use your modifications (patches) to compile "compatible" Wine version.

Look at the Picasa for Linux - it comes bundled with it's special Wine version. And of course Google has all changes available for download.

Dan Kegel · Post by **Dan Kegel** » Sat Mar 08, 2008 9:29 am

On Fri, Mar 7, 2008 at 8:15 PM, 3vi1 <[email protected]> wrote:

Doesn't the iPhone use an ARM CPU? How's WINE going to help you there?

He could compile his app as a winelib app.

This would be breaking new ground (Wine on OS/X on ARM), but it
will probably happen someday, so why not try it?

'Course, the app won't be very iPhone-y. But for some apps that might
not matter.
- Dan

3vi1 · Post by **3vi1** » Sat Mar 08, 2008 11:26 am

Dan Kegel wrote:On Fri, Mar 7, 2008 at 8:15 PM, 3vi1 <[email protected]> wrote:
Doesn't the iPhone use an ARM CPU? How's WINE going to help you there?
He could compile his app as a winelib app...

He could, but that's not what he described (with all due respect <g>)

Dan Kegel · Post by **Dan Kegel** » Sat Mar 08, 2008 11:36 am

On Sat, Mar 8, 2008 at 8:26 AM, 3vi1 <[email protected]> wrote:

Doesn't the iPhone use an ARM CPU? How's WINE going to help you there?
He could compile his app as a winelib app...
He could, but that's not what he described.

Can't use wine to run win32 x86 binaries on an arm;
you'd need an x86, emulator, too. And that'd probably
be too bloated for an iphone.

If you can recompile your windows app using winelib, you
can run it on non-x86 cpus without an emulator.

JÃ©rÃ´me Gardou · Sat Mar 08, 2008 12:56 pm

I guess that the goal would be to run applications written for windows CE.
Taht could be the beginning of wine support for this platform, as the API is
very close to the x86 version.

___________________________________________________________________________
Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire.
http://fr.mail.yahoo.com

Dan Kegel · Post by **Dan Kegel** » Sat Mar 08, 2008 1:37 pm

On Sat, Mar 8, 2008 at 9:53 AM, Jérôme Gardou <[email protected]> wrote:

I guess that the goal would be to run applications written for windows CE.
Taht could be the beginning of wine support for this platform, as the API is
very close to the x86 version.

Oh. D'oh! Yes, it would be cool to be able to run WinCE apps
on the iPhone. Somebody should try building Wine there
and see what happens

3vi1 · Post by **3vi1** » Sat Mar 08, 2008 2:11 pm

Dan Kegel wrote: Oh. D'oh! Yes, it would be cool to be able to run WinCE apps
on the iPhone. Somebody should try building Wine there
and see what happens

Can't disagree there... I need a replacement for my Dreamcast. :p

Dee Ayy · Post by **Dee Ayy** » Sat Mar 08, 2008 10:16 pm

Thanks for your replies.

I forgot about ARM. Apple just stresses that the iPhone uses the same
OSX that's already in use on other Macs.

I tried building only on Mac without MS Windows using winelib, but I
wasn't good enough. So I resorted to installing VMware Fusion on the
Mac, MS Windows in Fusion, and VC++ 6.0 in MS Windows as the API was
intended to be used, and was able to run the exe with Wine directly on
the Mac. Maybe I'll give winelib another try.

There was/(is?) Darwine for Power PC processors. It would be nice if
Wine could run on ARM.

Regarding the licensing as I understand, if I'm able to go the winelib
route, I'd also have to provide object files, "If you link other code
with the library, you must provide complete object files to the
recipients, so that they can relink them with the library after making
changes to the library and recompiling it."?

Regards.

vitamin · Post by **vitamin** » Sat Mar 08, 2008 10:56 pm

Dee Ayy wrote:Regarding the licensing as I understand, if I'm able to go the winelib
route, I'd also have to provide object files, "If you link other code
with the library, you must provide complete object files to the
recipients, so that they can relink them with the library after making
changes to the library and recompiling it."?

Not correct. It's your business what you do with your app. But if you modify Wine itself in any way shape or form, you have to provide all such modifications as the source files / patches. So that anyone can take stock Wine, apply your patches, recompile it and have your app working with it.

As far as distribution - it's up to you how you doing it. You can redistribute compiled (binary) Wine anyway you'd like. Wine is made to run from it's own install directory. This way you can have multiple versions in use at the same time.

Dan Kegel · Post by **Dan Kegel** » Sun Mar 09, 2008 10:10 am

On Sat, Mar 8, 2008 at 8:16 PM, Dee Ayy <[email protected]> wrote:

Regarding the licensing as I understand, if I'm able to go the winelib
route, I'd also have to provide object files, "If you link other code
with the library, you must provide complete object files to the
recipients, so that they can relink them with the library after making
changes to the library and recompiling it."?

That "just" means that users have to be able to
fix bugs in winelib by dropping in new .dll's.
So it's not really a showstopper, but using winelib
is messy in many ways.

You'd be better off going with plain wine for many reasons
if possible.