Mac to PC

[Gbowe]

I have just started using FileMaker Developer 5 on a MAC (G3 OS 9.1). When I bind my solution, it works fine on the Mac, but does not work on a PC (it is not recognised).

Do I have to bind all the files also on a PC, for them to work on Windows, or is it possible to do everything from the Mac?

Thanks

Ger

[danjacoby]

You need a Windows machine to create a Windows-compatible runtime solution.

Part of the reason for this is that there are several files (.DLL files, mostly) that are created along with the runtime solution and are specific to that application.

Yep, it's a pain in the neck. Perhaps, if Microsoft were to fall off the edge of the planet and everyone switched to Macs, we'd all be better off. But then again, whom would the Justice Department's antitrust division go after?

[Kurt Knippel]

quote:

---

Originally posted by danjacoby:

You need a Windows machine to create a Windows-compatible runtime solution.

Part of the reason for this is that there are several files (.DLL files, mostly) that are created along with the runtime solution and are specific to that application.

---

You also have to remember Windows naming conventions and include the ".fp5" at then end of the filename, so that the OS recognizes the type of file.

------------------

=-=-=-=-=-=-=-=-=-=-=-=-=

Kurt Knippel

Consultant

Database Resources

mailto:[email protected]

http://www.database-resources.com

=-=-=-=-=-=-=-=-=-=-=-=-=

[Ambush Bug]

Hello.

I have run into a similar stonewall regarding making a runtime for Windows. Am I to understand, now, that you cannot bind a solution on a Mac to be used on a PC, at all? If not, then what's the point of adding the solution extension and changing the file extensions when creating the runtime?

If it _is_ possible to bind a solution on a Mac to be used on a PC, then what am I doing wrong? (I ask that generally, so as to solicit a "procedure" of sorts not found in the handy dandy FM-Dev manual). I do indeed change the extensions, add an extension to the runtime (i use the default), and I also bundle the FM 'extensions' and 'support' folders (can't recall the names right now) onto the CD-R with the runtime... When I go to run on a PC, what's missing are the support files.

TIA all,

AB

[Kurt Knippel]

quote:

---

Originally posted by Ambush Bug:

Hello.

I have run into a similar stonewall regarding making a runtime for Windows. Am I to understand, now, that you cannot bind a solution on a Mac to be used on a PC, at all? If not, then what's the point of adding the solution extension and changing the file extensions when creating the runtime?

If it _is_ possible to bind a solution on a Mac to be used on a PC, then what am I doing wrong? (I ask that generally, so as to solicit a "procedure" of sorts not found in the handy dandy FM-Dev manual). I do indeed change the extensions, add an extension to the runtime (i use the default), and I also bundle the FM 'extensions' and 'support' folders (can't recall the names right now) onto the CD-R with the runtime... When I go to run on a PC, what's missing are the support files.

---

You cannot create runtimes on different platforms. There is simply no way to create a Windows application on the Mac or visa-versa. This is not possible in any programming language that I know of.

Functionanally the FMP Developer Edition is the same on both Mac and Windows which is why some options are available that do not really have a use on Mac.

------------------

=-=-=-=-=-=-=-=-=-=-=-=-=

Kurt Knippel

Consultant

Database Resources

mailto:[email protected]

http://www.database-resources.com

=-=-=-=-=-=-=-=-=-=-=-=-=

[Ambush Bug]

Aha! Thankye for stopping my futile search through the manual. I suppose FM-corp doesn't mind then, license-wise, that we are forced to install the same program on a Mac and a PC just to be able to use all of its functions (that's just my rhetorical irreverent self; no need for a response).

I wonder if they're hiring manual writers down there? Oh well... Onward.

AB the misled

[This message has been edited by Ambush Bug (edited March 02, 2001).]

[john.daly]

Just to add my bit to this discussion since I have exeprienced the reverse (compiling on a PC for use on a Mac). What you have to compile on the PC are the dll's and the exe file. Once you have these system files you can distribute your runtime database (fp5)files that you have produced on the Mac just as long as you continue to use the same binding code.

[Bill Jaynes]

Jumping in here, what about moving the bound solution from one platform to the other. Here's what I'm wondering. I am creating my solution on a PC. I'll bind it there, bundle it with an installer and burn a CD.

But I also want to do the same on my wife's MAC, that is port the unbound files to the MAC via floppies, get it working properly there(have done this with some tweaking), bind them and bundle with a compatible installer. Now, how do I get this solution out of the MAC which has neither a zip drive nor a CD burner.

Could I email the result to the PC with the burner and burn it there?

[dspires]

quote:

---

Originally posted by captkurt:

You cannot create runtimes on different platforms. There is simply no way to create a Windows application on the Mac or visa-versa. This is not possible in any programming language that I know of.

---

REALbasic (http://www.realsoftware.com/) allows exactly that.

[mikihasa]

Perl is cross platform, too. It works great--even on the Mac where there is no "command line" (yet).

Sorry of the off-topic post. I couldn't resist.

Just to be relevant, If you bind the solution on the PC and then bind it again on the Mac it should work on both platforms. For web distribution, I still put up both a PC and Mac version so Mac users don't have to download the useless DLLs and PC users don't have to get StuffIt.

I think that is what john.daly said in his post, so maybe instead of being relevant I am redundant...oh well.

Michael

[David McKee (Protolight)]

quote:

---

Originally posted by dspires:

REALbasic (http://www.realsoftware.com/) allows exactly that.

---

Well, not exactly. Again, the simple fact is that PowerPC 750 code cannot run on a Pentium III cpu-based computer, and vice versa.

No one program/application file can be run on machines with radically different cpus, sorry no prize for you.

-Dave