FM Server Licensing Question

Questions
81

To use LiveCode you will need:

  • 1024 x 768 or larger monitor
  • True color display (16-bit or 32-bit depth)
  • At least 256Mb of memory
  • At least 150Mb of disk space

Windows

The engine supports the following Windows OS

  • Windows 7 (both 32-bit and 64-bit)
  • Windows Server 2008
  • Windows 8.x (Desktop)
  • Windows 10 Note: On 64-bit Windows installations, LiveCode runs as a 32-bit application through the WoW layer.

Linux

LiveCode supports the following Linux distributions, on 32-bit or 64-bit Intel/AMD or compatible processors:

  • Ubuntu 14.04 and 16.04
  • Fedora 23 & 24
  • Debian 7 (Wheezy) and 8 (Jessie) [server]
  • CentOS 7 [server] LiveCode may also run on Linux installations which meet the following requirements:
  • Required dependencies for core functionality:
  • glibc 2.13 or later
  • glib 2.0 or later Optional requirements for GUI functionality:
  • GTK/GDK 2.24 or later
  • Pango with Xft support
  • esd (optional, needed for audio output)
  • mplayer (optional, needed for media player functionality)
  • lcms (optional, required for color profile support in images)
  • gksu (optional, required for privilege elevation support) Note: If the optional requirements are not present then LiveCode will still run but the specified features will be disabled. Note: The requirements for GUI functionality are also required by Firefox and Chrome, so if your Linux distribution runs one of those, it will run LiveCode. Note: It may be possible to compile and run LiveCode Community for Linux on other architectures but this is not officially supported.

Mac

The Mac engine supports:

  • 10.9.x (Mavericks)
  • 10.10.x (Yosemite)
  • 10.11.x (El Capitan)
  • 10.12.x (Sierra)
  • 10.13.x (High Sierra)
  • 10.14.x (Mojave)
  • 10.15.x (Catalina)
  • 11.x (Big Sur)
  • 12.x (Monterey)
  • 13.x (Ventura)

Note: The engine runs as a 32-bit application regardless of the capabilities of the underlying processor, unless you are on an OS that only supports 64 bit, or you have set it to 64 bit on on an earlier OS that supports 64 bit.

For development - deployment options are a larger scope

1 Like
82

One other option. 360Works MirrorSync can sync a FM (e.g. FMGo) application to any of a number of other DB, including MySQL, MS Sequel Server, Maria, etc... Write it in FM, store it in MySQL.

Here is an interesting use case. You can build an FM solution (FMGo, Pro), and MirrorSync that to a e.g. MySQL database, completely eliminating FMS in the process. You still need FMS to do the initial setup, but the performance and licensing issues become moot. I've not done this, but I've heard Jesse Barnum @ 360Works talk about it as deployment option.

Here is the link to 360Works help file and video on how to do this.