I'm making a Firemonkey application for both Windows and MacOS, and now I'm working on making it able to check online for updates and download the update. I have got it to work on Windows, by renaming the running .exe file, download the new one and then run the downloaded .exe, works as it should.
Now my problem is MacOS, I don't have much experience with MacOS, so I don't really have any idea how I should do this :/
And even less idea as I store somedata files inside the 'program.app' folder.
So I'd really appreciate some help or ideas on how I should try to solve this problem?
Apps on OSX are really just a package of files. If you go into finder on OSX and right click on an app you will see show package contents. Open that up and you will see the constituent files that make up the "app". From there you have to decide what you need to replace.
Related
I created an Unity game in Windows and I wanted to pass it to a Mac computer. I built it for Mac and I uploaded the .app folder to Google Drive as a .rar. Then, I downloaded it in a Mac and I unzipped it. When I try to open it, it shows the error message “Someapp.app can’t be opened”. It doesn’t explain why. I think the problem isn’t from Unity because the log file is empty after the error. Can anyone help me?
I needed to make the actual executable in the .app folder, well, “executable”.
Please try:
Open up a Terminal and navigate to your app folder:
cd <PATH_TO_YOUR_APP>/<APP_NAME>.app/Contents/MacOS/
This folder contains the actual executable file which Windows apparently didn’t make executable. Let’s add the executable flag:
chmod +x <APP_NAME>
Afterwards I could start the app.
I made the Build for my project for both PC and Mac, however I had massive issues getting the Mac one to actually work. Here is the tutorial I used to make the builds which was suppppper helpful, but it didn't help fix my issue:
https://www.youtube.com/watch?time_continue=3&v=7nxKAtxGSn8&feature=emb_title
I just figured out how to make the Mac build work with a friend and it was a bit of work. Once you follow the video's directions exactly for the Mac version, you can send the file to your Mac but when you do it will be labeled MacOS and then when you try to open it it will most likely fail and say missing application to open.
From what I have learned, this is because the compression actually corrupts the executable file to open it on the Mac. To fix this, you have to use Terminal to navigate your way into the file and unlock the permission settings that were changed due what we believe is from the compression.
I honestly can't remember where I found this code but the navigation part I got from the other answer here, but you need to open up a Terminal and navigate to your app folder:
cd <PATH_TO_YOUR_APP>/<APP_NAME>.app/Contents/MacOS/
and add the following:
chmod -R 777 [applicationName].app
This unlocked the permissions on the application but when the app was opened, we had to allow permission through the Mac firewall to let it run on the computer. Once we approved permission, the app ran no problem.
I hope this helps and I'm by no means a professional with this so but my friend and I can try to help in anyway possible.
I'm trying to use "wine" on MAC osX Sierra version 10.12, wine is version 1.9.19
In the terminal I can launch Windows applications, however its a pain to have to keep typing in:
/Applications/Wine\ Staging.app/Contents/MacOS/wine ~/.wine/drive_c/Program\ Files/HeidiSQL/heidisql.exe
I've searched around for a post on how to create shortcuts/applications to add to the launchpad, but so far none of the information has led me to a working end result. Either the locations of wine is different or it just doesn't work.
I've tried creating an application script:
do shell script "/Applications/Wine Staging.app/Contents/MacOS/wine ~/.wine/drive_c/Program Files/HeidiSQL/heidisql.exe"
But this won't run either.
For anyone having the same problem, in the end I created scripts which reside in my home folder:
Launch vi, create a file called HeidiSQL, insert:
wine ~/.wine/drive_c/Program\ Files/HeidiSQL/heidisql.exe
Save and exit file, grant file execute permissions:
chmod +x HeidiSQL
Launch wine terminal and type in ./HeidiSQL to launch, I then did the same for PSPad.exe:
wine ~/.wine/drive_c/Program\ Files\ \(x86\)/PSPad\ editor/PSPad.exe
I know this thread is a little old but I was just looking for something like this to launch HeidiSQL and I came up with these three solutions which I have tried and all of them work. I am putting my findings down here for it may help someone:
Wineskin (http://wineskin.urgesoftware.com), Playonmac (https://www.playonmac.com/en) and Winebottler
(http://winebottler.kronenberg.org)
Wineskin is a mac app that download and install (and manages, updates, etc) "wine" for you. It then creates a HeidiSQL.app (any name you want with any icon you want - but you need to configure it) around the windows.exe that includes the wine version selected and is completely self contained (does not need wine installed separately). Personally this is the neatest solution and my preferred even though there its a little more technical than Playonmac and similar to Winebottler. You need to read the instructions (which are very good) and you have choices to make as to the wine version to use and to configure the app. Noteworthy is that you need to change the windows version to XP rather than 7 or some buttons won't work.
Playonmac on the other hand is very user friendly. It has HeidiSQL listed on its website as compatible and its almost a single click install. You just select HeidiSQL from the list of programs and it will download everything you need for you. The only reason I prefer Wineskin is that it does not create a true self contained HeidiSQL.app. You can create a shortcut for it in your Applications folder but this will launch Playonmac and the app needs to be installed inside Playonmac. On the plus side, Playonmac will chose all the right settings for you to run the app correctly, the correct windows and wine version etc which is something you need to fiddle with with with Wineskin.
Winebottler again makes an app like Wineskin. The only real difference I could see is that with Wineskin the configuration app is actually part of the package whereas in Winebottler you have to recreate the package each time you make a change. I stuck with Wineskin. YMMV.
I've created software using Filemaker and I have to create an installer.
I already done it for Windows but I have to create one for Mac too. The installer will be able to install the software, install a font and ask the serial number.
Can someone help me?
I think Apple used to (still does?) offer a program with Xcode that was called PackageMaker, but I don't think they still do. It might be available from a previous version of Xcode. I found surprisingly little information about it online.
However, the command line tools that it was based on, pkgbuild, productbuild, and pkgutil , seem to be installed on my laptop running Yosemite with an Xcode utilities installation.
I would check out the accepted answer to a similar question here on Stack Overflow. It looks quite detailed, but I think it's going to be very advanced work to get a successful package created.
The above is what you probably want if you want your installer to use Apple's own Installer app. If all you want is to create an installer that gets the job done, I would probably use FileMaker itself.
Create a FileMaker file that stores your solution within a container field, lock it down with security and scripting, use Export Field Contents to get the solution file and your fonts to the right places, perhaps with some supporting AppleScript that makes use of the command line. Use FileMaker Advanced to package this up as a runtime solution and all the user has to do is double-click the runtime app and you can guide them from there. Once the installation is complete you could even open the installed solution for them and prompt them at that point to enter a serial number.
I have tried in vain to install JDK on a flash drive. I have seen many threads on how to do this, but, I do not see one which addresses my issue. I have JDK on my PC already. No matter if I Run from the website or save to the desktop or flash drive itself, when I double click the Java icon to install, I do not have an opportunity to select any installation preferences. It just runs the configuration then tells me the files already exist. Even when I save to the flash and click the icon within my flash folder, it still tries to install on the PC.
Any ideas?
Thanks.
There's a hacky way to do this that I don't recommend, but apart from copying the files directly to flash drive, this is the only solution I can think of. The Java installer is likely detecting your registry key for the one you already have installed. I don't recommend doing this unless you know what you're doing, but deleting the folders in:
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit
May have it skip the check and just install it. I recommend you write down what you modified in the registry and make sure that you can re-create it before doing this. If this works as I think it will, the Java installer should not detect the other version of Java on your computer, and you should be able to proceed with installation. I still recommend just copying the appropriate directories to your flash drive instead though, Chris B has the right idea.
Note: This is my first answer. I hope I was able to help you! If not, let me know in the comments so I can do my best to get you to the optimal solution you are looking for! :)
I am a windows developer and I had to port an app to Mac. I built it fine and have everything working except my installer. I built my Package file (.pkg) which installs fine and works great on a Mac.
However, I want to move the file to a windows OS over a network to upload it to an ftp server. My ftp client is on Windows. I have done this before without issues on previous .pkg files but I just created one that is acting strange. When I view most .pkg files in windows explorer, they are treated almost like an unknown file type. Windows lets me see the file but I can't really do anything with it. This is fine because I just want to move the file, not use it in any other way.
Unfortunately, I have a new .pkg file that windows strangely treats like a directory instead of just a single file. I can open it and see the "Contents" folder and some internal files/binaries/whatever that I don't want to see. While this is similar to the MacOS functionality, it causes problems because it is uploaded as a directory rather than a file. I just want to drag it to my server and let people download it. Why is this happening?
I have looked online a fair amount and nobody seems to have this issue. It does seem to be permissions related. I saw a good amount of people complaining about "Custom Access" and oddly enough, when I click "get info" on the file, it does say I have "custom access". .Pkg files that seem to display correctly in windows explorer do not have this set. Anyways I would really appreciate the help. I could probably just get an ftp client on the Mac but this does seem really strange and it may help others if there is a solution.
Historically, Mac OS X installer files have been built as bundles, or a directory that appears as a file in OS X. These types of installers will always appear as directories in Windows. However, Mac OS X 10.5 added support for a new format, which is simply the important parts of the installer compressed using xar. Since this format is an archive and not a bundle, it will show up as a single file in Windows.
PackageMaker can produce either format depending on the minimum target version you specified for the package. If you specify 10.5, it will create the new xar format, but if you specify an older version, it will create a bundled installer. If your application will only work for 10.5 and later, you can change the minimum version in PackageMaker by going to Project > Install Properties (Command+I) and changing the Minimum Target dropdown. If you want to support older versions of OS X, then your only choice is to create the bundle version and either compress it as a zip file, or create a disk image to hold it.