Is there a way to ask them directly?
I inspected my current x86 setup.exe, you can download it from
SourceForge:
http://sourceforge.net/projects/openchrom/files/REL-0.9.0/openchrom_0.9.0_rel_x86_win-setup.exe/download
There are some NSIS references stored in the binary, but I'm not
sure either if it's due to the normal specification of Windows *.exe
files or if they are NSIS specific:
$ strings openchrom_0.9.0_rel_x86_win-setup.exe | grep NSIS
http://nsis.sf.net/NSIS_Error
NSIS Error
<?xml version="1.0" encoding="UTF-8"
standalone="yes"?><assembly
xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0"><assemblyIdentity version="1.0.0.0"
processorArchitecture="X86" name="Nullsoft.NSIS.exehead"
type="win32"/><description>Nullsoft Install System
v2.46-7</description><dependency><dependentAssembly><assemblyIdentity
type="win32" name="Microsoft.Windows.Common-Controls"
version="6.0.0.0" processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df" language="*"
/></dependentAssembly></dependency><trustInfo
xmlns="urn:schemas-microsoft-com:asm.v3"><security><requestedPrivileges><requestedExecutionLevel
level="highestAvailable"
uiAccess="false"/></requestedPrivileges></security></trustInfo><compatibility
xmlns="urn:schemas-microsoft-com:compatibility.v1"><application><supportedOS
Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/><supportedOS
Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/></application></compatibility></assembly>
Philip
Am 06.11.2014 um 18:21 schrieb Wayne
Beaton:
Certainly interested. We've invested some thought into this
already; the uDig project has started the IP due diligence process
on it.
One thing that I'm not all that clear on is how much of the NSIS
intellectual property actually ends up in the installer (i.e.
there must be some NSIS runtime bits included in the
distribution). Is this something that is relatively easily
determined?
Wayne
On 06/11/14 12:18 PM, Philip Wenig
wrote:
Hi
Denis,
if it's of interest: I'm using NSIS to bundle my RCP application
for Windows users since some years now:
http://openchrom.wordpress.com/2011/09/06/microsoft-windows-users-love-setup-files
I'm quite happy cause NSIS allows to build the setup.exe files
under Linux too! :-). The executable is build using a shell
script, triggered after a successful Maven/Tycho product build
of my application. Furthermore, I also have automation scripts
to build *.deb and *.rpm files. Only Mac OS X *.dmg images can't
be produced under Linux, cause the hdiutil command line programm
is missing.
If you'd like to, I'm willing to share my scripts.
Best,
Philip
Am 06.11.2014 um 17:45 schrieb Denis Roy:
Greetings CBI followers,
I've been wondering about the feasibility of building the
Eclipse launchers using CBI... I'm referring to the
eclipse.exe and "eclipse" executable files that start Eclipse.
If I am not mistaken, those files are currently being build
elsewhere, and are deposited somewhere (Git?) to be consumed
by EPP.
If these files could be built by CBI, I'm guessing they could
be made slightly more intelligent to help detect the
presence/absence of a JRE and offer usable help to our users.
This would be part of the overall plan to help improve the
initial user experience to Eclipse, as outlined below:
https://wiki.eclipse.org/Eclipse_User_Experience_2015
The actual bug to track this effort is:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=377116
Thanks for any input you have!
Denis
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev
--
~~~~~~~~~~~~~~~~~~~~~~~~
Dr. Philip Wenig
http://www.openchrom.net
https://www.xing.com/profile/Philip_Wenig
http://de.linkedin.com/pub/philip-wenig/2a/4a8/877
~~~~~~~~~~~~~~~~~~~~~~~~
|
