• How To Install Wine
• Install Wine Mono On Kali

Packages for openSUSE Leap 15.2. Wine-mono-6.3.0-lp152.37.1.noarch.rpm wine-mono-6.3.0-lp152.37.1.src.rpm. Install Wine 5.0 on Ubuntu (not valid for Linux Mint) First, remove existing Wine install with this command: sudo apt remove winehq-stable wine-stable wine1.6 wine-mono wine-geco winetricks. Then make sure to add 32-bit architecture support: sudo dpkg -add-architecture i386.

Info

How to Install Slack on CentOS 8 Slack is a very popular application used for communicating and collaborating with the team members of a company or an organization. You can have an individual or group discussion in a channel, share files and images, and have a video or audio call for quick collaboration with your teammates and make quick decisions. This popup tells the user to install Wine, and points them to the Linux Support page, even though the Launcher is running on Mac. If a shell script is specified in execs.json as an alternative to a batch script, the Launcher will attempt to launch the shell script defined for Linux, even if a different shell script is defined for Darwin (MacOS).

Don’t expect that you can build app for all platforms on one platform.

• If your app has native dependency, it can be compiled only on the target platform unless prebuild is not used.

  prebuild is a solution, but most node modules don’t provide prebuilt binaries.

• macOS Code Signing works only on macOS. Cannot be fixed.

Free public Electron Build Service is used to build Electron app for Linux on Windows. On macOS/Linux you can build Electron app for Windows locally, except Appx for Windows Store (in the future (feel free to file issue) electron-build-service will support Appx target).

You can use build servers — e.g. Travis to build macOS/Linux apps and AppVeyor to build Windows app.

By default build for current platform and current arch. Use CLI flags --mac, --win, --linux to specify platforms. And --ia32, --x64 to specify arch.

For example, to build app for MacOS, Windows and Linux:

Build performed in parallel, so, it is highly recommended to not use npm task per platform (e.g. npm run dist:mac && npm run dist:win32), but specify multiple platforms/targets in one build command.You don’t need to clean dist output before build — output directory is cleaned automatically.

Sample .travis.yml to Build Electron App for macOS, Linux and Windows¶

Sample appveyor.yml to Build Electron App for Windows¶

Use AppVeyor only if:* you need to build AppX,* or your app has native dependency and prebuilt binary is not provided.

Otherwise see above sample .travis.yml to build Windows on Linux using provided Docker image.

macOS¶

All required system dependencies (except rpm) will be downloaded automatically on demand on macOS 10.12+ (macOS Sierra). On Travis, please add osx_image: xcode10.2 (see above sample .travis.yml).

To build rpm: brew install rpm (brew).

Linux¶

You can use Docker to avoid installing system dependencies.

To build app in distributable format for Linux:

To build rpm: sudo apt-get install --no-install-recommends -y rpm (or sudo yum install rpm-build).

To build pacman: sudo apt-get install --no-install-recommends -y bsdtar.

To build snap if and only if you have custom stage packages (if you don’t have custom snap build configuration, you don’t need to install). See snapcraft in Store.

To build app for Windows on Linux:¶

Docker (electronuserland/builder:wine) is recommended to avoid installing system dependencies.

• Install Wine (2.0+ is required) — see WineHQ Binary Packages.
• Install Mono (4.2+ is required) if you want to use Squirrel.Windows (NSIS, default target, doesn’t require mono).

To build app in 32 bit from a machine with 64 bit:¶

Travis Linux¶

Xenial is required.

Travis macOS¶

macOS 10.14+ is required.

Docker¶

To build Linux or Windows on any platform.

Warning

You cannot build for Windows using Docker if you have native dependencies and native dependency doesn’t use prebuild.

See example Docker usage on a CI server in the sample .travis.yml.

Note

Do not use Docker Toolbox on macOS. Only Docker for Mac works.

Build Electron App using Docker on a Local Machine¶

1. Run docker container:

2. Type in yarn && yarn dist

If you don’t have dist npm script in your package.json, call ./node_modules/.bin/electron-builder directly.

Or to avoid second step, append to first command /bin/bash -c 'yarn && yarn dist' You can use /test.sh to install dependencies and run tests.

Tip

If you don’t need to build Windows, use image electronuserland/builder (wine is not installed in this image).

Provided Docker Images¶

• electronuserland/builder or electronuserland/builder:12 — NodeJS 10 and required system dependencies. Based on builder:base. Use this image if you need to build only Linux targets.
• electronuserland/builder:wine — Wine, NodeJS 10 and required system dependencies. Based on builder:10. Use this image if you need to build Windows targets.
• electronuserland/builder:wine-mono — Mono for Squirrel.Windows. Based on builder:wine. Use this image if you need to build Squirrel.Windows target.
• electronuserland/builder:wine-chrome — google-chrome-stable and xvfb are available — you can use this image for headless testing of Electron application. Based on builder:wine.
• electronuserland/builder:base — Required system dependencies. Not supposed to be used directly.

Flashpoint's Mac support is heavily experimental. This page provides information about the current Flashpoint for Mac package.

Please join our Discord and provide your feedback: http://discord.gg/S9uJ794

• 2Installation Instructions
  • 2.1Troubleshooting
• 3Technologies

Latest Package

Download Beta 2019-12-15:

Changelog:

2019-12-15: Added 'wmode':'direct' to the default SWFObject parameters. This fixes certain 3D Flash games which previously did not work properly.

2019-12-14: First beta available!

Installation Instructions

1. Download and unzip the latest package using the link above.
2. Double-click StartFlashpoint.command to open Flashpoint.
   • Do not forget this step! You must use StartFlashpoint.command, otherwise Flashpoint will not work properly.

Troubleshooting

If Flashpoint does not work after installation, follow the steps below:

1. Click the Apple menu and open System Preferences.
2. Click 'Security & Privacy,' then click the 'Privacy' tab.
3. Click 'Full Disk Access'.
4. Click the lock icon and enter your password to make changes. Then click the + button under the list of apps to add Terminal to the list.
5. Click the lock icon again to save your changes. You should see Terminal in the list of allowed apps, as shown below.
   

Flash EOL Screen

If you see the Flash Player EOL information screen when you try to play a game, that means that SeaMonkey is loading your installed Flash Player plugin instead of the plugin that is bundled with Flashpoint. To fix the problem, uninstall Flash Player from your Mac and restart Flashpoint. Games should work again in SeaMonkey.

MacOS Catalina and Big Sur

Because Flashpoint's applications are from an 'unidentified developer,' if you're using Catalina or Big Sur, you'll need to approve each application before it can run. Open your system preferences, click 'Security & Privacy', then allow each of the following applications to run: StartFlashpoint.command, Flashpoint Launcher, swfbbox, and SeaMonkey. If you have trouble figuring out how to do this, watch this tutorial video.

Because Adobe Director Projectors are 32-bit applications, SPR for Mac will not work on MacOS Catalina or Big Sur. This means that Flashpoint for Mac does not support Shockwave games on Catalina or Big Sur.

MacOS Big Sur (MacOS 11.0)

Flash applications have been successfully tested and are working. To use Flashpoint with Big Sur, a few modifications are required. Follow the steps below:

1. Download SeaMonkey 2.53.4 for MacOS x64 from here: https://www.seamonkey-project.org/releases/
2. Open Flashpoint Infinity's FPSoftware folder, then find the old 'SeaMonkey.app' there.
3. Right-click the old SeaMonkey.app and click 'Show Package Contents.'
4. Open the Contents folder, then within that folder, open the Resources folder.
5. Find the folder called plugins and copy it.
6. Find the new 'SeaMonkey.app' file that you downloaded by searching in Finder under 'This Mac'.
7. Right-click the new 'SeaMonkey.app' and click 'Show Package Contents.'
8. Open the Contents folder, then within that folder, open the Resources folder.
9. Paste in the plugins folder that you copied earlier.
10. Go back outside of the new 'SeaMonkey.app' package and copy it.
11. Open Flashpoint Infinity's FPSoftware folder, then paste the 'SeaMonkey.app' file that you just copied. Replace the original file when prompted.

Apple Silicon Macs

To run Flashpoint on Macs with the new M1 chip, you'll need to install Rosetta by following these instructions. Once you've done that, follow the instructions in the previous sections to get Flashpoint working.

Installing Java

To add support for Java games, you'll need to install the Java Development Kit. Follow the steps below:

1. Download JDK version 8u212 from here: https://github.com/frekele/oracle-java/releases/download/8u212-b10/jdk-8u212-macosx-x64.dmg
2. Open the DMG file and run the installer. Follow the on-screen instructions to install the JDK.

Installing Wine

Running games in Wine is not yet supported, but we hope to add support for this in a future build. If you'd like to contribute to our efforts, you can download an installer here.

Using Flashpoint with Automator (optional)

You can start Flashpoint without having to click on StartFlashpoint.command by using Automator using the below steps:

1. Choose File > New.
2. Select 'Application', then click Choose.
3. Drag the Run Shell Script action into your workflow.
4. Enter open /Users/[YOUR USERNAME HERE]/Downloads/Flashpoint Infinity for Mac Beta/StartFlashpoint.command in the command field.

Technologies

Currently, only Flashpoint Infinity is available for Mac. However, as explained here, both PHP and Apache are included with MacOS. This means it should be fairly simple to create a Flashpoint Ultimate package for MacOS as well. Let us know in our Discord if you can help!

Install Wine Mac Os

No equivalent to the Flashpoint Redirector currently exists for MacOS. MacOS also does not provide any native way to set per-application proxy settings. In Flashpoint for Mac, the proxy settings for each supported technology must be set separately. This rules out using the Flash projectors, since they do not have configurable proxy settings. In Flashpoint for Mac, all Flash games run in a browser.

The Flashpoint FAQ contains a list of all web game technologies ('Platforms') supported in the Windows version of Flashpoint. The Mac version currently supports a small subset of these platforms. This is explained in detail below. The list of supported platforms includes an unscientific estimate of the percentage of games supported by our method.

Supported Platforms

• Flash: Supported using the SeaMonkey web browser, with a Flash plugin included. Games that use a Flash Player version other than 32 are not yet supported.
  • ~95% of games supported.
• Shockwave: Supported with SPR for Mac. Because LeechProtectionRemovalHelp is only available for Windows, the majority of Shockwave games will not work properly.
  • ~30% of games supported.
  • Requires a 32-bit compatible OS; Catalina is not supported.
• HTML5: Supported using the SeaMonkey web browser. WebAssembly support is enabled in Flashpoint's SeaMonkey profile, so it should be compatible with nearly all of the same games as Basilisk.
  • ~99% of games supported.
• Java Applets: Supported natively using the JDK. Java in the browser is not supported yet.
  • ~99% of games supported.

Unsupported Platforms

• Unity Web Player: Has not been attempted yet. We would need to track down the Mac builds of all 12 versions of Unity Web Player that we support on Windows. Needless to say, this would be a huge challenge.
• PopCap Plugin: As far as we know, there is no version of PopCap Plugin for modern Macs.
• Authorware Web Player: Authorware is incompatible with all Intel Macs.
• GoBit Plugin: As far as we know, there is no version of GoBit Games Plugin for modern Macs.
• Silverlight: Silverlight for Mac is available here, but as explained in this StackExchange answer, Microsoft Silverlight for Mac is 32-bit only, even though the Windows version has 64-bit and 32-bit versions. This is a problem because no major browser for MacOS has a 32-bit version, and MacOS Catalina drops support for 32-bit programs entirely. As such, Silverlight is unusable on Mac.
• 3DVIA Player: As far as we know, there is no version of 3DVIA Player for modern Macs.
• 3D Groove GX: 3D Groove is incompatible with all Intel Macs.
• ActiveX: ActiveX is a Windows-only technology.
• ShiVa3D: The Windows version of the ShiVa3D Player is available in the free ShiVa Web Edition; this is where we obtained it. However, no Mac version of the ShiVa Web Edition is currently available, so we haven't been able to find a Mac version of the ShiVa3D Player. It's possible that we could extract a Mac version of the player from a Mac version of a ShiVa3D game. Or maybe we could obtain the Mac runtime from the Windows version of ShiVa3D Web Edition, since it has the capability of publishing for Mac.

Launcher Issues

A number of Flashpoint Launcher issues affect the experience of using Flashpoint Launcher on MacOS. Unfortunately, none of our Launcher developers currently have access to a Mac, so updates for the Mac version of Flashpoint Launcher will not be available in the foreseeable future. We will be unable to release a Mac version of Flashpoint 7.0 until a new version of the Launcher is built for MacOS. If you have access to MacOS and are able to build Flashpoint Launcher, please let us know!

The current issues with the Mac version of Flashpoint Launcher are listed below.

• Errors are shown in the log when services are missing from the services.json. These services are unnecessary for Flashpoint on Mac, so the errors can be ignored.
• Flashpoint Launcher cannot find its own Version file, even if it is present in the Launcher's folder and app package.
• The Theme dropdown menu on the Config tab does not work properly. To select a theme, you must manually type the path to the theme's CSS file.
• A popup appears if the user attempts to start a Windows executable from Flashpoint. This popup tells the user to install Wine, and points them to the Linux Support page, even though the Launcher is running on Mac.
• If a shell script is specified in execs.json as an alternative to a batch script, the Launcher will attempt to launch the shell script defined for Linux, even if a different shell script is defined for Darwin (MacOS).
• Flashpoint Launcher attempts to load the hidden resource forks of certain files as separate files. These files are not visible in the MacOS Finder, and have filenames beginning with ._.
  • If any Platform XML has a resource fork, all of the Platform XMLs will fail to load, causing a 'No games found' error.
  • If any localization JSON file has a resource fork, a 'NotValidJSON' error will appear in the logs.
• When Wine is started from Flashpoint Launcher, it uses >70% CPU for several minutes without ever starting the intended executable. This is despite Wine working fine when started from the terminal. This issue needs to be investigated and solved before Flashpoint can support launching games through Wine.
• By default, Flashpoint Launcher will attempt to read and modify config.json and preferences.json inside its own app package. Since Mac applications are not allowed to modify their own app packages, this will fail. For this reason, Flashpoint Launcher must be opened with a shell script command StartFlashpoint.command. This script sets the current directory to the Flashpoint Launcher folder so that the Launcher accesses the config.json and preferences.json in the correct location. However, this unusual way of opening the Launcher may be the cause of the previously mentioned Wine bug.

Other Notes

Macos Install Wine

• Some keyboard controls such as the spacebar or WASD keys may not work in some games. This is a known problem with the NPAPI Flash plugin on MacOS. We plan to resolve this problem in the next build of Flashpoint for Mac by using the PPAPI plugin instead.
• Flash games with URLs pointing to filenames with special characters will not work. This is because nosamuEmbedSWF.sh does not properly handle special characters when it converts URLs to paths, so it cannot copy the game's HTML to the correct location in htdocs.
• Some Shockwave games may not close when you quit them from the menu. If this occurs, click inside the Message Window next to the game. Then type quit and press Enter to close the game.
• Flashpoint for Mac uses exec mappings to determine what native executable to run based on the specified Windows application path. For example, flashplayer_32_sa.exe is mapped to nosamuEmbedSWF.sh for MacOS. To add more exec mappings, navigate to Flashpoint's Data folder and open execs.json in a text editor. The exec mappings use 'darwin' to refer to MacOS.
• Flashpoint for Mac uses swfbbox to determine the width and height of an SWF file. swfbbox is part of the swftools homebrew package. To install swftools, first install homebrew. Then type brew install swftools in the terminal.
• Flashpoint for Mac requires that PHP and cURL are enabled on your system. These components should be enabled by default.

Packaging Flashpoint for Mac

Macos Install Wine Mono

Here are some steps to keep in mind when packaging Flashpoint for Mac. This assumes that you are using the current package as a base and modifying it.

• You can follow these instructions to update Flashpoint's XMLs to the latest version.
• You can follow these instructions to update Flashpoint Router to the latest version.
• Use update-spr.sh in the FPSoftware folder to update SPR to the latest version. To get the latest version of SPR for Mac, see SPR for Mac.
• If you would like to distribute a modified SeaMonkey profile, be sure to clear the cache, cookies, and other data. In SeaMonkey, click Tools -> Clear Private Data.
• If you would like to add a plugin to SeaMonkey, first install the plugin normally. Then, follow these steps:
  1. Navigate to /Library/Internet Plug-Ins in Finder and copy the files for the plugin you want to add.
  2. Navigate to Flashpoint's FPSoftware folder. Right-click SeaMonkey.app and choose 'Show Package Contents.'
  3. Inside the app package, navigate to /Contents/Resources/plugins. Paste the plugin files that you copied in Step 1.
• Before running or distributing Flashpoint, you should run the dot_clean command inside the Flashpoint folder to remove resource forks. Flashpoint Launcher may not work properly if Flashpoint files have resource forks, as explained in Launcher Issues.

Install Wine Mac Os

Mono is an open-source and cross-platform implementation of the .NET Framework. Wine can use a Windows build of Mono to run .NET applications.

• 1Installing

Installing

From source

From a source tree, you can use the 'make dev' target to build Wine Mono and configure the current Wine prefix (default or as set by the WINEPREFIX environment variable) to use the build. The 'make dev-setup' target will just configure the Wine prefix without building.

Shared Install

For packagers, and users with multiple prefixes, a shared install is recommended.

To create a shared install, download the appropriate binary tarball from https://dl.winehq.org/wine/wine-mono/ (or build it from source with 'make bin') and extract it to the appropriate location.

Wine will search for Wine Mono in the following places (replacing 5.0.0 with the expected version):

• c:windowsmonomono-2.0. Extracting a tarball here is not recommended. If you want to install into a specific prefix, use the Prefix Local Install instructions below. It's only included in this list to make it clear that an installed .msi takes priority over the other loctions.
• The directory specified in HKEY_CURRENT_USERSoftwareWineMono string value 'RuntimePath'.
• ${prefix}/share/wine/mono/wine-mono-5.0.0 or ${builddir}/../mono/wine-mono-5.0.0
• /usr/share/wine/mono/wine-mono-5.0.0
• /opt/wine/mono/wine-mono-5.0.0

When using a shared install, The 'Wine Mono Windows Support' package must still be installed in the prefix. This is handled automatically on prefix update, so normally it shouldn't be a problem, but in some corner cases you might have to run 'wineboot -u' to set this up after creating the shared install.

Prefix Local Install

Wine will automatically download and install the appropriate Wine Mono MSI on prefix update, so this shouldn't usually be necessary.

If you wish to use a different MSI installer than the one you'd get automatically:

• Obtain the MSI file you wish to use, either from https://dl.winehq.org/wine/wine-mono/ or by running 'make msi' in a build tree. It's possible you already have the one you want in ~/.cache/wine.
• Run 'wine uninstaller' and remove 'Wine Mono Runtime' and 'Wine Mono Windows Support' if you have them.
• Run 'wine msiexec /i path/to/wine-mono.msi'

Versions

Building

For build instructions, see the readme at https://github.com/madewokherd/wine-mono

Debugging

As of Wine Mono 0.0.4, the WINE_MONO_TRACE environment variable may be set as follows to trace calls within Mono:

This option is the same as the --trace option in Mono.

Note that 'All assemblies' includes the program itself and all libraries shipped with it. Mono is capable of tracing any .NET code. You probably should avoid the 'all' trace if there might be proprietary code running in the process.

Activating any trace at all, even a bogus assembly name, will cause Mono to print out all exceptions as they occur. This can be useful, but it can also be misleading as some exceptions are perfectly normal.

If you're not sure which libraries might be involved in a problem, and no exceptions are being raised, try WINE_MONO_TRACE=wrapper. It tends to be low-traffic while also containing useful information.

Sometimes Mono's inlining can obscure the source of an exception, especially NotImplementedException. This can be worked around by setting MONO_INLINELIMIT=0.

Setting WINE_MONO_VERBOSE=1 will display the addresses of all JIT-compiled methods. Setting MONO_VERBOSE_METHOD=MethodName will display detailed information about the method, and break into the debugger if one is attached.

Documentation

Standard .NET namespaces and classes are documented at MSDN here: http://msdn.microsoft.com/en-us/library/w0x726c2.aspx

Test Suite

As of 5.0, Wine Mono includes a test shell which can run tests from Mono and a few of its own. In the future, it'd be nice to include tests from some of the .NET Core projects as well.

The tests can be built using 'make tests' in the build tree or downloaded from https://github.com/madewokherd/wine-mono/releases. The 'make tests-zip' target will build a zip file for running outside the build tree.

To run the full test suite in Wine, use the 'make test' target.

To run the full test suite in Windows, use run-tests.exe with no arguments.

Both of these methods use a default set of -skip-list, -pass-list, and -fail-list command-line switches to skip certain unreliable tests and to determine which tests are expected to pass or fail. Since these are only tested on Esme's build machine, and even there they are unpredictable, expect some unexpected results.

Specific test names can be passed to run-tests.exe as arguments, for example:

run-tests.exe can be used in the same way on native Linux Mono, or .NET on Windows. It can also be used with the native Mono inside a Wine Mono build tree with the mono-env script:

How To Install Wine

Note that this particular Mono environment is only intended for building Wine Mono components, and may not accurately reflect the state of upstream Mono.

Test source code can be found in tools/tests, mono/mono/tests, and mono/mcs/class/*/Test. See https://www.mono-project.com/community/contributing/test-suite/ for information on Mono's tests.

Microsoft .NET

Install Wine Mono On Kali

If you need to use Microsoft's implementation of the .NET framework, the Microsoft runtimes can partly run on Wine. You can find tips and share comments with other users at the .NET AppDB page.

You can install the appropriate version of Microsoft's .NET runtime (dotnet35, dotnet30, dotnet20, or dotnet11) through winetricks. Be aware though, that your .NET application still might not work (at least not yet), and Microsoft's .NET runtimes are not free software so be sure to read the EULA before accepting. Mono, on the other hand, is free software and probably a better choice if it works with your application.

.NET Core and .NET 5.0 are different from .NET Framework 4.x and earlier. They are no longer implemented as an OS component, and as such they can work just fine alongside Wine Mono, or alongside earlier .NET Framework versions. Applications relying on .NET 5 will usually include the runtime, meaning that it won't be necessary for users to install it, but the installers should also work fine.

Wine Mono does not make any attempt to implement or replace .NET 5, nor are there any plans to do so. The architectures are very different, and there hasn't been demand for a .NET 5 replacement.