THE NEW RELEASE OF THE PORTABLEAPPS.COM INSTALLER IS HERE:
https://portableapps.com/node/19015
The PortableApps.com Installer allows you to easily create a custom installer for any app without having to write any code. You just need to edit a simple configuration file that has comments within and have the latest NSIS and the FindProc and MoreInfo plugins installed on your PC.
The current version of the installer is 0.12.4 and it was released on 2009-03-12. You can download the current installer as well as the localization files from here:
Download PortableApps.com Installer 0.12.4 [56K download / 145K unzipped]
MD5: 22db2806392b4ee2456a3db978e5841f
The download includes the following files:
PortableApps.comInstaller.bmp - the banner that is shown on the left-hand side
PortableApps.comInstaller.nsi - the actual code (this file may not be edited)
PortableApps.comInstallerConfig.nsh - the configuration file which should be edited as the included comment guidelines indicate (no custom code may be added to this file)
PortableApps.comInstallerLANG_*.nsh - localization files for different languages
As you read through PortableApps.comInstallerConfig.nsh, you'll see that you have many options in terms of files to remove and keep. For most installers, removing the App and Other directories is sufficient when upgrading.
For applications with plugins and other files that may reside in the App directory that you wish to keep, you can define individual directories and files to preserve. This will allow you to keep, for example, the App\Example\plugins
directory even though you've set the App directory to be removed.
The end result is that your installer is greatly simplified and it removes the need for most developers to have to do a WinMerge on the previous and new version, determine what files and directories to remove and then write the NSIS code to do so.
In the off chance you do need custom code, you can still set the config file to allow it and then include your custom code within a file called PortableApps.comInstallerCustom.nsh. In there, you can define macros that will be run pre install, post install and pre install when the optional section of a multi installer is not selected. These macros must be named CustomCodeOptionalCleanup, CustomCodePreInstall and CustomCodePostInstall. All are optional.
Using The Installer
- Unzip the files to your application's Other\Source directory in a standard PortableApps.com Format layout
- Edit the PortableApps.comInstallerConfig.nsh file appropriately for your application
- Then include the LANG files that you are using in the installer. One if single language, as needed if multiple languages.
- When done, compile the installer by right-clicking on the PortableApps.comInstaller.nsi file in Windows Explorer and selecting Compile NSIS Script (requires NSIS and the FindProc and MoreInfo plugins installed on your PC)
- When complete, the directory above your AppNamePortable directory (usually X:\PortableApps) will contain your installer
NOTE: You can usually speed up compile time by doing the above off a fast hard drive (internal or external) rather than a slower flash drive.
Updating the Installer and Config
All releases with the same point number use the same config file layout. So, your config file from PortableApps.com Installer 0.12.1 will work fine, unchanged with 0.12.3. We only make changes on point releases and major releases. 0.13 would have a different config file layout.
The PortableApps.com Installer has full support for: Afrikaans, Albanian, Arabic, Basque, Bulgarian, Catalan, Croatian, Czech, Danish, Dutch, English, Estonian, Farsi, Finnish, French, German, Greek, Hebrew, Hungarian, Indonesian, Italian, Japanese, Korean, Latvian, Lithuanian, Macedonian, Norwegian, Polish, Portuguese, Portuguese (Brazilian), Romanian, Russian, Serbian (Latin), Simplified Chinese, Slovak, Slovenian, Spanish, Spanish (International), Swedish, Thai, Traditional Chinese, Ukranian
The PortableApps.com Installer has partial support (Welcome and Finish pages and a few strings will be in English) for: Belarusian, Bosnian, Breton, Galician, Icelandic, Irish, Kurdish, Luxembourgish, Malay, Mongolian, Norwegian Nynorsk, Serbian, Turkish, Uzbeck, Welsh
If you'd like to assist with one of these languages we're missing our translation for, you can do so in the Localization: PortableApps.com Installer 0.12.x & up forum thread.
New Release Notification
If you'd like to get an email notification when a new version of the PortableApps.com Installer is released, you can just by using your SourceForge.net account and monitoring the PortableApps.com Installer package.
Please post any comments or suggestions.
Thanks,
John
Future additions:
- Add installer generator from appinfo.ini
Release History:
- 0.12.4 (2009-03-12): Fix for installer hang when refreshing the menu with Platform 1.5
- 0.12.3 (2009-03-02): Fixed Catalan, Serbian, Swedish, Uzbek, Spanish International translations
- 0.12.2 (2009-02-27): Added afrikaans, albanian, arabic, basque, bulgarian, catalan, croatian, czech, danish, farsi, finnish, greek, hebrew, indonesian, korean, latvian, lithuanian, macedonian, norwegian, romanian, serbianlatin, slovak, slovenian, swedish, thai and ukranian translations
- 0.12.1 (2009-02-23): Fixed a translation (not used in any apps)
- 0.12.0 (2009-02-20): Fixed Polish, added Hungarian, updated to new versioning format
- 0.11.2 (2009-02-15): Added ability to pre-select optional component when doing a non-English install (useful for multilingual installers) and updated trademarks
- 0.11.1 (2009-02-02): Fixed typo in "ukranian" includes
- 0.11.0 (2009-01-20): Multilingual and single-language installers now supported. Considered a pre-release.
- 0.10.5 (2009-01-07): VersionCompare support in custom code. removed silent install (was mistakenly enabled previously, causes bugs and bypasses space checks, option checks, etc)
- 0.10.4 (2008-00-00): Blank suffixes now supported
- 0.10.3 (2008-00-00): Plugin installers now have special naming
- 0.10.2 (2008-00-00): Fixed plugin mode bug that required files in root
- 0.10.1 (2008-00-00): Fixed custom code issue
- 0.10.0 (2008-08-05): Initial public release
Thanks John for this great new direction. Great idea!
This makes it tons easier so newbies aren't overwhelmed by the amount of code they have to edit. This is wonderful, John!
There's no place like 127.0.0.1
... nothing more to say!
Paid for Software more or less?
What You need is OSS!
The only other feature I see missing is the ability to install all or part of the app to CommonFiles like in the Java portablizer or Perl Portable.
formerly rayven01
That'll be handled differently. We're only gonna support a couple things in Common Files and they'll be as special installers for that. And we'll be able to bundle those installers with apps when really needed. (Think GTK+ installer inside Pidgin with local installs)
Sometimes, the impossible can become possible, if you're awesome!
Is it possible to put an APPNAME constant so that there's less typing to do?
Insert original signature here with Greasemonkey Script.
It's been discussed a couple times and the answer is still no. I assume you're thinking that while looking at this:
So let's walk through it again. The AppName part of NAME and SHORTNAME are going to be different for several apps "Mozilla Firefox, Portable Edition" and "FirefoxPortable" for instance. The AppName part of FILENAME will be different again for some "Firefox_Portable_3.0.1_en-us" for instance. And the AppName part of CHECKRUNNING AND CLOSENAME may not even be the portable AppName it could be the regular appname "pidgin-portable.exe" and "Pidgin" for instance.
So, we can not save time with another variable and you only have to fill out this information *ONE* time for each app. So please can we stop asking about this now people?
Sometimes, the impossible can become possible, if you're awesome!
Okay, I think I'm going to drop an encyclopedia on my foot now...
Insert original signature here with Greasemonkey Script.
Wouldnt it better to get rid of the ;!define REMOVEDATADIRECTORY part?
Cause it shouldnt be used anyway and if I need it I can do it via custom codes. I just think it might be better if we make it as hard as possible to delete the users Data.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
The old multi-installer had a part where you performed an action if the option wasn't selected, ie:
What's the preferred method of doing this now?
Edit: nevermind, I just noticed the end of your post. Must have missed it on first read-through.
formerly rayven01
0.10.2 fixes a bug where plugin installers accidentally tried to include files from the root directory
Sometimes, the impossible can become possible, if you're awesome!
Version 0.10.3 allows plugin installers to now be named PortableApps.comInstallerPlugin.nsi and the associated config file to PortableApps.comInstallerPluginCustom.nsh to avoid overwriting the main app installer.
Sometimes, the impossible can become possible, if you're awesome!
Where can I find PortableApps.comInstallerLANG_English.nsh?
cowsay Moo
cowthink 'Dude, why are you staring at me.'
I found PortableApps.comInstallerLANG_English.nsh in the Source folder in Notepad++
its included in each of the latest apps
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
Why doesn't he put it here?
it's actually just the
!insertmacro "Lang_English"
part in the old installers (keep in mind we want to be multilingual ;).Insert original signature here with Greasemonkey Script.
I'm not sure why, but when I add more then one component installer doesn't show descriptions and during compilations NSIS displays warnings: "macro:MUI_DESCRIPTION_TEXT:5".
You shouldn't be changing the installer period. All you should need to edit would be:
PortableApps.comInstallerConfig.nsh
which would be(edited for my latest app, which I shall post up in about 5 minutes):
If you need custom code, you would use:
PortableApps.comInstallerCustom.nsh
The installer itself SHOULD NOT BE EDITED
Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world
If you will forgive my impertinence in posting a bug-fix, here it is, and it fixes a few major bugs with components in the installer. (All of these bugs are at the very end, with the component installer section.) The bug becomes apparent if you want to have more than one word in the component installation to stick into appinfo.ini. Normally, you won't want to, as it'll stick on "(English)" or "(Multilingual)", but in the case of BPBible, I needed "(App only)" and "(App with WEB and KJV)", so it didn't work.
With my fixes:
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
I must have lost those double quotes when replacing something else. It's fixed in 0.10.4.
Sometimes, the impossible can become possible, if you're awesome!
Do I have to edit the PortableApps.comInstallerConfig.nsh every time I update?
Unless anything else has been changed (which John should say), you'll just need to change following line to say the latest version.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
From about 0.10.1 or .2 forward as long as the second digit is unchanged, the existing config file will work. When I add or change config stuff it'll go to 0.11.
Sometimes, the impossible can become possible, if you're awesome!
Is there any particular reason why the following line:
isn't:
also, could an additional Copyright define be added, something similar to the additional Trademarks define.
All the others are spaceless, so it was for consistency.
No additional copyrights are added as the installer is copyright PortableApps.com.
Sometimes, the impossible can become possible, if you're awesome!
Okay, but when you right click on an executable file and click properties, on the 'Version' tab, Windows actually puts spaces in the following:
FileVersion
InternalName
LegalTrademarks
OriginalFilename
ProductName
ProductVersion
PrivateBuild
SpecialBuild
And the following:
CompanyName
become:
Company
Also, custom versioninfo strings don't get treated the same way.
Personally, I think it would be better to have spaces in it, but, it's your script.
Well, it's a bit too late now as we got lots of apps with it out as is. It'll be used by a later release of the Platform to understand how to communicate with some of the installers, so we'll be sticking with it as is. That's actually the main point of that custom string. Probably 99.99% of people will never see it, so we're not as worried about formatting.
Sometimes, the impossible can become possible, if you're awesome!
Hi,
how can I create an addon/plugin installer that adds files to the data directory? I have figured out how to add files to the other and app folders, but I have problems with adding files to the data folder.
The additional files should be copied to the $APPDATA folder, which is redirected to the Settingsdirectory (data\settings\appdata).
You can only add them directly (by storing them in Data\Settings\AppData within the directories) since APPDATA will be a LOCAL variable in the context the installer is run.
Sometimes, the impossible can become possible, if you're awesome!
but I guess you misunderstood my problem.
If the App folder is empty, the compilation will fail.
If I add a file to the App folder, the compilation will work.
But the created package includes only the Other and App subfolders, not the Data subfolder.
Well, have I missed an option in the Installer or InstallerConfig or isn't it possible to adjust the Installer so that files in the Data subfolder will be included.
It's for plugin installers. Plugins go in the App directory. Stuff that would go in Data isn't considered plugins, so it won't work. What are you trying to do so we can see if it would make sense to update the installer code?
Sometimes, the impossible can become possible, if you're awesome!
I found a workaround.
I want to create an addons pack for Dia portable. It will include additional objects, shapes and sheets.
Normally you could add new ones to the $APPDATA folder, in case of Dia Portable this is Data\settings\.dia .
But you could add them to App\Dia too. If you have a local install and add them in the programdirectory, they will be available for all users.
So either I'll create an addons pack this way or I'll include the addtional files in Dev Test 2.
I downloaded the above but was unable to install it with the reason that system cannot find an installer. Could you assist resolve this. I am anxious to get working with it. Thanks
St
Error function: FindProcDLL::FindProc "${CHECKRUNNING}"
you need the FindProcDLL plugin
The developer formerly known as ZGitRDun8705
Version 0.10.5 adds in the ability to use VersionCompare within custom code (which is first used by Notepad++ Portable 5.1.3) allowing an installer to easily check if upgrading from a specific version or earlier (useful for updates where file layouts change, etc). Silent installs are also disabled, they were mistakenly enabled earlier but have multiple issues including bypassing of free space checks, bypassing of options and bypassing of EULAs.
Sometimes, the impossible can become possible, if you're awesome!
Thank you John, will update
BTW, FWIW - up above in the Release History you listed the last release as a 2008 release as opposed to 2009, John.
You can delete this post after fixing it :P~
__
JG
I've updated the installer to add full multilingual support, all settable within the config file. If multilingual, you'll get a language picker on launch for the end user to pick their language unless they've launched from the upcoming PortableApps.com Platform 1.2 or 2.0 Alpha in which case it will automatically appear in their chosen language.
Sometimes, the impossible can become possible, if you're awesome!
Hi John,
I tested the new Installer (0.11.1), but I had the same problem mentioned here.
Altough I've included all languages included in your PortableApps.com_Installer_0.11.1.zip-file, I could only choose "German, English, Spanish, Dutch, Italian, French and Portuguese" when installing.
That is by design. NSIS is not a Unicode-aware app, which is why it still works on Windows 95/98/Me which several of our apps still support. So, it can not display, for example, Japanese if you have Windows set as English with the primary language. You can only select the languages the current PC is capable of displaying. As 99.99% of people will be running the installer on a PC in their native tongue or capable of displaying it, it's not a big deal at the moment. Once NSIS goes Unicode (which should hopefully be soon) we'll switch over to that and it won't be an issue. Their is an unofficial NSIS Unicode build now but it doesn't work with many plugins that we use and may have bugs.
Sometimes, the impossible can become possible, if you're awesome!
Thanks for the explanation!
Not an update to the installer, but I added the notes about the MoreInfo plugin being required as it was inadvertently omitted from the requirements.
Sometimes, the impossible can become possible, if you're awesome!
Hi John,
I don't know if that makes sense to you, but how about introducing a new variable $INSTALLDIRECTORY to the Installer and InstallerConfig? Usually it's the same as $SHORTNAME, but for some Addons or Plugins it could be useful.
I could use it for my Diashapes Portable. It is an addon for Dia Portable, so the $SHORTNAME and $INSTALLDIRECTORY are different. In the past I changed the Installer code (5 lines).
In the new Installer I'll have to change line 40, 572, 579, 586 and 590. I'll replace $SHORTNAME by my $INSTALLDIRECTORY (DiaPortable).
Thoughts?
What you do is include the files within a directory structure. So you'd actually have it all contained in the appropriate place. It would get pointed to X:\PortableApps\DiaPortable automatically (or by the end user), but within that, you'd have the appropriate directories in your file structure (NOT in the installer code). All our plugins and addons work like this. End users should have have to browser directory structures within portable app's directories to install add-ons, the installer must do it for them.
Sometimes, the impossible can become possible, if you're awesome!
Diashapes Portable would get pointed to X:\PortableApps\DiaShapesPortable automatically (using the standard installer). And that isn't the right path. It should get pointed to X:\PortableApps\DiaPortable automatically. Therefore I'll have to change the code.
IMHO Diashapes is only an addon with his own name.
The shortname should be DiaPortable, NOT DiaShapesPortable. Shortname is only used for the install directory. The long name can be whatever you want.
If you alter the installer code, it's no longer a PortableApps.com Installer.
Sometimes, the impossible can become possible, if you're awesome!
Shortname is only used for the install directory
Well, nope, look at your code.
If you alter the installer code, it's no longer a PortableApps.com Installer.
Ok, so I'll drop the popular Diashapes Portable. I don't want to create my own Installer fork
Look at it again and tell me what else it's used for.
Sometimes, the impossible can become possible, if you're awesome!
John, thank you for all your great work here. PortableApps.com is really a great project.
I made a suggestion for the installer, you don't like it. That's ok. It was only a suggestion, forget it.
You wrote "If you alter the installer code, it's no longer a PortableApps.com Installer.". I accept that, but all I want is to create a great package that makes it easy for the end users. And I'm an end user too, not really a dev. In the majority of cases it's enough to change the InstallerConfig.nsh. But in my opinion Diashapes Portable is an exception.
Maybe I could change the $SHORTNAME to DiaPortable (even if the variable is used somewhere else), but I'll have to alter the PortableApps.comInstallerPlugin.nsi anyway.
Why? I want to use the icon PortableApps.comInstallerPlugin.ico, so I comment out the lines 96 and 99-102 in the PortableApps.comInstallerPlugin.nsi.
You ask yourself why that noob doesn't define PLUGININSTALLER "true" in the PortableApps.comInstallerPluginConfig.nsh (line 121)? If I do that, the Diashapes Portable launcher won't be included in the package. So my small tweaks are necessary.
Conclusion: You don't allow to alter the installer, so the easiest decision for me is to drop Diashapes Portable. Rather no Diashapes Portable than a crappy one.
Just my 2 cents.
Even if you did alter the plugin installer, your method would NOT work with the new Platform anyway (it ignores EXEs in the root directory and uses the appinfo.ini directly, so your launcher would just be ignored by the platform).
Like I said, there is a reason that everything is setup the way it is. So developers don't go trying random things and wind up with things that don't work right. The apps, installer and platform are designed to work together and if you make a random change to one, it won't work with the rest.
Now, if you want assistance doing DiaShapes the right way, please start a new topic in the dev forum explaining what you're trying to accomplish rather than just assuming you need to create your own way or give up.
Sometimes, the impossible can become possible, if you're awesome!
No offense, but that's ridiculous!
For me, the new Platform is a dream of the future! I haven't seen an alpha, beta or something else from the new platform. Once it is released, my packages will work with it.
And btw., there are many other releases that wouldn't work with the new Platform too, because the included appinfo.ini is messy.
I apologize to you for this post. Maybe it sounds rude, I don't know. I don't want to be rude, but my apps are better than my english
I still love PortableApps.com and all the apps here!
If you really need a launcher (and you should NOT for addons... addons are additions to a main app, not a new way of starting an existing app), you will need to release it as a SEPARATE APP. The PortableApps.com Format Specification is designed like this. It really is a new app and should be treated as such even though it works with Dia and will only work with Dia next to it.
For an example of this, just look at the Private Browsing by PortableApps.com. It launches Firefox within the FirefoxPortable directory and doesn't include it in itself. Technically, you could think of it as an addon to Firefox Portable, but it is treated as a different app by the platform and spec.
I may release an optional launcher just for the Thunderbird Portable address book at some point (if I don't wind up including it as a secondary icon) for folks who want it. That will also be released as its own app in a new directory but look to the ThunderbirdPortable directory next to it.
Sometimes, the impossible can become possible, if you're awesome!
Rather than argue in circles any further, I decided to just package it up myself to show that it can be done and to demonstrate the proper way of handling a separate app like this that interlinks with an existing one. Full details are here:
https://portableapps.com/node/16648#comment-111477
Sometimes, the impossible can become possible, if you're awesome!
First of all I want to say a huge thank you for PortableApps.com; this is an amazing site and I always recommend it to friends and work colleagues. I think it is fanatastic that the PortableApps.com Installer has been made available for free and free to try making your own apps. Here is the problem; I think I have done everything correctly, but then the compiler returns the following errors:
Error while loading icon from "..\..\App\AppInfo\appicon.ico": can't open file
Error in script "C:\Documents and Settings\####\Desktop\CCleanerPortable\Other\PortableApps.comInstaller.nsi" on line 100 -- aborting creation process
I have been attempting to make CCleaner portable as a test. By the way, I have never done this before (excuse my ignorance), but I am really interested in the whole process. If someone is willing to walk me through things a bit it would be much appreciated.
Am I not creating the correct folder structure?
Is it a question of not editing the .nsh file properly?
Any help or advice would be greatly appreciated.
Thanks in advance,
Mark Rose
You haven't included all of the proper files for PortableApps.com Format on which the PortableApps.com Installer depends. It's looking for the App\AppInfo\appicon.ico file it uses and it's not there. Complete details are here:
https://portableapps.com/node/12851
Also, not that you can't redistribute a repackage version of CCleaner. They don't permit it.
Welcome to PortableApps.com
Sometimes, the impossible can become possible, if you're awesome!
I added the ability to have the optional component be auto-selected when the user selects a non-English install. This is useful for multilingual apps where we leave off the translations on an English install but install them otherwise (GIMP, Pidgin, etc) and will reduce issues of non-English users accidentally not installing their needed language.
The trademarks and copyright were also updated.
Sometimes, the impossible can become possible, if you're awesome!
whats the status with the installer and using it with non open-source apps? some people have been asking on IRC lately about thi.
But there’s no sense crying over every mistake,
You just keep on trying till you run out of cake.
It's not quite ready yet but will be when we have the generator. Just finished the multilingual bits. Now finishing the downloader bits. Then the first test generator is released.
We've allowed a couple popular apps to do it already. Like Free Commander. And Mikogo. And we'd allow other publishers of popular apps directly. But we're not allowing people repackaging freeware from others yet.
Sometimes, the impossible can become possible, if you're awesome!
0.12 fixed the Polish translation and adds Hungarian. Stub language files for translations we don't have are now included.
I've also introduced a change to versioning. From now on, the config files are versioned as 0.12.x meaning that they will work for all 0.12.* releases. When we do sub-point releases like 0.12.1, your existing configuration files will not change. We'll use sub-point releases for language additions and fixes as well as bug fixes and minor enhancements that don't impact the configuration file. This will make it easier for developers to keep up to date on the installer.
Sometimes, the impossible can become possible, if you're awesome!
Because i currently have no idea how the optional components are supposed to work. I would like to make my installer optionally install source files (among other things), and i am curious as to how this would be achieved.
i used the !define MAINSECTIONTITLE "AppName Portable (English) [Required]" section in the PortableApps.comInstallerConfig.nsh file to get one optional component, but i am unsure of how exactly even this component should be set up. How do i place the files in the ${SHORTNAME}Optional1\ directory so that they are later placed in the /Other/Source directory on install?
Thanks!
You'd place them in ${SHORTNAME}Optional1\Other\Source. So if your app was AppNamePortable, you'd place them in AppNamePortableOptional1\Other\Source
Sometimes, the impossible can become possible, if you're awesome!
But how can i have multiple options? is there a way?
It's really only meant for selecting whether or not to install localizations besides english for multilingual apps when they add a lot of install size. It may be limited to that in the future.
Source should be a separate download. Other stuff should be done as add-ons usually.
Sometimes, the impossible can become possible, if you're awesome!
Is there any reason why the Data directory might not be packed into the installer, or, if this is the expected behavior, is there any way to get the installer to include the files in the \Data directory?
My Launcher depends on the settings in \Data\Settings.ini, and without this file, it gives the user several errors about not being about to read the file, then cannot find litestep(.exe), so it pukes and dies, killing explorer, and leaving the user with no active shell.
All apps in PortableApps.com Format are required to be able to recreate the structures they need within the Data directory if they do not exist. The installer does not include the data directory or it would overwrite an end user's settings on an upgrade.
Sometimes, the impossible can become possible, if you're awesome!
0.12.2 updates the included languages. Your current 0.12.x config file doesn't need any changes. The following languages have been added (translators listed after):
afrikaans - PollieXmas
albanian - truri
arabic - mazaya
basque - gaztelugatxe
bulgarian - orax
catalan - Fremen,jfalonso
croatian - igy
czech - jacob_opengate
danish - vkcelik
farsi - mahdiit
finnish - Kimmo
greek - DawnDeath
hebrew - DarkSlim
indonesian - msubali,cornelius,adjayanto
korean - sushizang,pakcw
latvian - Kaspars Krampis
lithuanian - waidis
macedonian - RatShot
norwegian - Saltvann
romanian - th3wildwolf
serbianlatin - mrmot
slovak - black_
slovenian - andrej72
swedish - Faffe,Patrik
thai - psisci
ukranian - AIBinas
Sometimes, the impossible can become possible, if you're awesome!
I just posted an update with fixes for Catalan, Serbian, Swedish, Uzbek, Spanish International. No config changes are necessary.
Sometimes, the impossible can become possible, if you're awesome!
Thanks for fixing this up so quickly.
This release fixes a hang when trying to refresh the PortableApps.com Platform 1.5 on a few systems. It properly refreshes both the 1.5 and 1.5.1 Menu. All developers are urged to update their apps to this new release. We won't be doing revisions of released stable apps for it at this point, but all other apps should be updated. The upgrade is easy as it is a drop-in replacement for any app using any 0.12.x installer.
Sometimes, the impossible can become possible, if you're awesome!
SectionIn: [RO]
SetOutPath: "$INSTDIR"
SectionGetFlags: 1->$0
IntOp: $0=$0&1
IntCmp $0:1 equal=MainSkipOptionalCleanup,
File: "..\..\*.*" -> no files found.
Usage: File [/nonfatal] [/a] ([/r] [/x filespec [...]] filespec [...] |
/oname=outfile one_file_only)
Error in script "C:\tmp\CodeBlocksPortable\Other\Source\PortableApps.comInstaller.nsi" on line 953 -- aborting creation process
I'm a newbie at this stuff. What did I do wrong?
The installer is only for use with apps in PortableApps.com Format (PAF). Form that, it looks like there's nothing in the root directory of the app you're trying to package (which is required by PAF specs).
Sometimes, the impossible can become possible, if you're awesome!
Thanks for the amazingly fast answer.
How do I create that file?
For example: I have the latest Codeblocks + mingw setup inside \CodeBlocksPortable\App\CodeBlocks\. I followed the guide to the letter. How do I get the \CodeBlocksPortable\CodeBlocksPortable.exe file which run it?? Is ther any program that generate it??
Thanks
You can base it on the launchers used by other apps. They're all written in NSIS, the development environment you installed to get the PortableApps.com Installer running. Or you could write your own in C++ or any language really (except .NET-based languages since they are not portable). We're going to have an easy to use generic one soon that won't require you to do this, but it's not ready yet.
Sometimes, the impossible can become possible, if you're awesome!
as I'm putting the finishing touches on my Code::Blocks Portable which handles a shared MinGW etc. in a much more polished way than previously done in any attempts. Additionally, Code::Blocks stores its settings in a relatively complex way, which make it unlikely that you could sort it out without experience in such things. I've sorted out the best way though.
If you're looking at making launchers though, read the field guide and look at some apps - the launcher source code goes in Other\Source\AppNamePortable.nsi.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
I'd be glad to have someone else sort it out.
Are you using the latest nightly build? will it be possible to substitute TDragon gcc build instead of the mingw one?
How long will it take you to finish?
Thanks
Dave
Hello
Please add a feature to your installer that will allow for installation to more than one directory, eg; multiple USB drives.
Thanks in advance,
Panarchy
This can't be done at all with any installer systems. They only support a single installation directory.
And this is a feature which would be used by practically no one. So it won't happen – even if it were technically possible.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
Hello
Why wouldn't this be possible?
Normal installers can install to multiple directories, why not the PortableApps installer?
Hang on a second, can the Installer also install into sub-directories?
Please tell me if it can.
Thanks in advance,
Panarchy