NSIS Wiki - User contributions [en]

Aero plug-in

2015-10-31T14:05:38Z

Faph: conda execute links

{{PageAuthor|Afrow UK}}

== Description ==
Enables Windows Aero glass effect on NSIS UI. Supported on Windows Vista, 7 and 8.

http://nsis.sourceforge.net/mediawiki/images/a/ad/Aero.png

== Download ==
<attach>Aero.zip</attach>

Run with <code>conda execute</code> or install with <code>conda install</code> (see [[Conda]]).

Stu

[[Category:Plugins]]

AccessControl plug-in

2015-10-31T14:03:43Z

Faph: conda execute links

{{PageAuthor|tbf}}

== Links ==
<attach>AccessControl.zip</attach> (includes NSIS-Unicode variant)

Run with <code>conda execute</code> or install with <code>conda install</code> (see [[Conda]]).

[http://support.microsoft.com/kb/243330 Well-known security identifiers in Windows operating systems]

== Description ==

'''Version:''' 1.0.8.1 (7th July 2014)

'''Supported on:''' ''WinNT4+''.

The AccessControl plugin for NSIS provides a set of functions related to Windows NT access control list (ACL) management.

== Usage Example ==
<highlight-nsis>
# Give ownership for file C:\test.txt to Waterloo\Mathias
AccessControl::SetFileOwner \
"C:\test.txt" "Waterloo\Mathias"
Pop $0 ; "error" on errors

# Make the directory "$INSTDIR\database" read write accessible by all users
AccessControl::GrantOnFile \
"$INSTDIR\database" "(BU)" "GenericRead + GenericWrite"
Pop $0

# Give all authentificated users (BUILTIN\Users) full access on
# the registry key HKEY_LOCAL_MACHINE\Software\Vendor\SomeApp
AccessControl::GrantOnRegKey \
HKLM "Software\Vendor\SomeApp" "(BU)" "FullAccess"
Pop $0

# Same as above, but with a numeric string SID
AccessControl::GrantOnRegKey \
HKLM "Software\Vendor\SomeApp" "(S-1-5-32-545)" "FullAccess"
Pop $0
</highlight-nsis>

''Detailed usage instructions and a list of functions can be found in the package readme Docs\AccessControl\AccessControl.txt.''

== File and Directory Permission List ==

=== File Permissions ===
* ReadData
* WriteData
* AppendData
* ReadEA
* WriteEA
* Execute
* ReadAttributes
* WriteAttributes
* Delete
* ReadControl
* WriteDAC
* WriteOwner
* Synchronize
* FullAccess
* GenericRead
* GenericWrite
* GenericExecute
* NULL

=== Directory Permissions ===
* ListDirectory
* AddFile
* AddSubdirectory
* ReadEA
* WriteEA
* Traverse
* DeleteChild
* ReadAttributes
* WriteAttributes
* Delete
* ReadControl
* WriteDAC
* WriteOwner
* Synchronize
* FullAccess
* GenericRead
* GenericWrite
* GenericExecute
* NULL

=== Registry Permissions ===
* QueryValue
* SetValue
* CreateSubKey
* EnumerateSubKeys
* Notify
* CreateLink
* Delete
* ReadControl
* WriteDAC
* WriteOwner
* Synchronize
* GenericRead
* GenericWrite
* GenericExecute
* FullAccess
* NULL

'''See also:''' [http://msdn2.microsoft.com/en-us/library/aa364399.aspx File Security and Access Rights] 
'''See also:''' [http://nsis.sourceforge.net/Talk:AccessControl_plug-in Set the append/modify flag for ACLs] 
'''Comment:''' The GenericWrite permission isn't the same like the one on the microsoft page.

== Credits ==
Written by [http://taschenorakel.de/mathias/ Mathias Hasselmann] 
NSIS-Unicode port by [http://wizou.fr Olivier Marcoux] 
Major changes by [http://www.afrowsoft.co.uk Afrow UK] 
Win95/WinNT4 support and bugfixes by [[User:Anders|Anders]]

[[Category:Plugins]]

Registry plug-in

2015-10-30T18:13:11Z

Faph: conda execute links

{{PageAuthor|Instructor}}

== Links ==

Download v4.1: 
<attach>Registry.zip</attach>

Discussion: 
[http://forums.winamp.com/showthread.php?s=&threadid=223066 Forum thread]

Run with <code>conda execute</code> or install with <code>conda install</code> (see [[Conda]]).

== Description ==

This is NSIS plug-in for registry. Archive also contains PPC-Registry plugin for Pocket PC.

'''Features:'''
*Powerful registry search:
**fast algorithm
**principle of turn in stack (first in -> last out)
**i.e. search from first registry key to last
**search for key, value and/or string in any root
**search with name and/or type
**search with banner support
**search with subkeys or not
*Check if registry key exists
*Read value of any type and size
*Write value of any type and size
*Create key
*Delete value (same as DeleteRegValue)
*Delete key (same as DeleteRegKey)
*Delete empty key (if no values and subkeys in it)
*Copy value
*Move value
*Copy key
*Move key
*Export key contents to the file in ansi REGEDIT4 or unicode REGEDIT5 format
*Import key contents from the file to the registry (Note: this does not work on Windows Vista)
*Converts string to hex values
*Converts hex values to string

== Usage ==

=== Open for search ===

<highlight-nsis>
${registry::Open} "[fullpath]" "[Options]" $var
</highlight-nsis>
=== Find first and next (call one or more times) ===
<highlight-nsis>
${registry::Find} "[handle]" $var1 $var2 $var3 $var4

From ReadMe file

"[handle]" handle returned by registry::Open

$var1 "[path]"
$var2 "[value]" or "[key]"
$var3 "[string]"
$var4 "[TYPE]"
TYPE:
"" -Search is finished
"BANNER" -Banner is used, return only path
"REG_KEY" -Registry key is found
"REG_BINARY" -Raw binary data
"REG_DWORD" -Double word in machine format (low-endian on Intel)
"REG_DWORD_BIG_ENDIAN" -Double word in big-endian format
"REG_EXPAND_SZ" -String with unexpanded environment variables
"REG_MULTI_SZ" -Multiple strings, next string separated by new line '$\n'
"REG_NONE" -Undefined type
"REG_SZ" -Null-terminated string
"REG_LINK" -Unicode symbolic link
"REG_RESOURCE_LIST" -Device-driver resource list
"REG_FULL_RESOURCE_DESCRIPTOR" -Resource list in the hardware description
"REG_RESOURCE_REQUIREMENTS_LIST" -
"REG_QWORD" -64-bit number
"INVALID" -Invalid type code

</highlight-nsis>

=== Close search (free memory) ===
<highlight-nsis>
${registry::Close} "[handle]"
</highlight-nsis>

=== KeyExists (check if registry key exists) ===
<highlight-nsis>
${registry::KeyExists} "[fullpath]" $var

$var == 0 # key exists
$var == -1 # key doesn't exist
</highlight-nsis>

=== Registry Read ===
<highlight-nsis>
${registry::Read} "[fullpath]" "[value]" $var1 $var2
</highlight-nsis>

Where:
* $var1 is the value read.
* $var2 is the type read:
** "" - no value
** "REG_BINARY"
** "REG_DWORD"
** "REG_DWORD_BIG_ENDIAN"
** "REG_EXPAND_SZ"
** "REG_MULTI_SZ"
** "REG_NONE"
** "REG_SZ"
** "REG_LINK"
** "REG_RESOURCE_LIST"
** "REG_FULL_RESOURCE_DESCRIPTOR"
** "REG_RESOURCE_REQUIREMENTS_LIST"
** "REG_QWORD"
** "INVALID"

=== Registry Write ===

<highlight-nsis>
${registry::Write} "[fullpath]" "[value]" "[string]" "[TYPE]" $var

$var == 0 # success
$var == -1 # error
</highlight-nsis>

=== Registry Extra Read ===

<highlight-nsis>
${registry::ReadExtra} "[fullpath]" "[value]" "[number]" $var1 $var2
</highlight-nsis>

=== Registry Extra Write ===

<highlight-nsis>
${registry::WriteExtra} "[fullpath]" "[value]" "[string]" $var

$var == 0 # success
$var == -1 # error
</highlight-nsis>

=== Create Registry Key ===

<highlight-nsis>
${registry::CreateKey} "[fullpath]" $var
$var == 1 # [fullpath] already exists
$var == 0 # [fullpath] successfully created
$var == -1 # error
</highlight-nsis>

=== Delete Registry Value (same as DeleteRegValue) ===

<highlight-nsis>
${registry::DeleteValue} "[fullpath]" "[value]" $var

$var == 0 # success
$var == -1 # error
</highlight-nsis>

=== Delete Registry Key (same as DeleteRegKey) ===

<highlight-nsis>
${registry::DeleteKey} "[fullpath]" $var

$var == 0 # success
$var == -1 # error
</highlight-nsis>

=== Delete Empty Registry Key (if no values and subkeys in it) ===

<highlight-nsis>
${registry::DeleteKeyEmpty} "[fullpath]" $var

$var == 0 # success
$var == -1 # error
</highlight-nsis>

=== Copy Registry Value ===

<highlight-nsis>
${registry::CopyValue} "[fullpath_source]" "[value_source]" "[fullpath_target]" "[value_target]" $var

$var == 0 # success
$var == -1 # error
</highlight-nsis>

=== Move Registry Value ===

<highlight-nsis>
${registry::MoveValue} "[fullpath_source]" "[value_source]" "[fullpath_target]" "[value_target]" $var

$var == 0 # success
$var == -1 # error
</highlight-nsis>

=== Copy Registry Key ===

<highlight-nsis>
${registry::CopyKey} "[fullpath_source]" "[fullpath_target]\[new_key_name]" $var

$var == 0 # success
$var == -1 # error
</highlight-nsis>

=== Move Registry Key ===

<highlight-nsis>
${registry::MoveKey} "[fullpath_source]" "[fullpath_target]\[new_key_name]" $var

$var == 0 # success
$var == -1 # error
</highlight-nsis>

=== Registry Export (save to the file in REGEDIT4 format) ===

<highlight-nsis>
${registry::SaveKey} "[fullpath]" "[file]" "[Options]" $var

$var == 0 # success
$var == -1 # error
</highlight-nsis>

=== Registry Import (restore from the file) ===

<highlight-nsis>
${registry::RestoreKey} "[file]" $var

$var == 0 # success
$var == -1 # error
</highlight-nsis>

Note:
${registry::RestoreKey} simply exec regedit: regedit /s "[file]"

=== StrToHex (converts string to hex values) ===

<highlight-nsis>
${registry::StrToHex} "[string]" $var
</highlight-nsis>

"[string]" - String to convert

$var - Hex string

=== HexToStr (converts hex values to string) ===

<highlight-nsis>
${registry::HexToStr} "[hex_string]" $var
</highlight-nsis>

"[string]" - Hex string to convert

$var - String

=== Unload plugin ===

<highlight-nsis>
${registry::Unload}
</highlight-nsis>

== Tips ==
=== REG_QWORD "Gotcha" ===
When writing values they must be in a quoted hex string exactly 16 characters long.
==== Example ====
<highlight-nsis>
## Set the QWord value to 0
${registry::Write} "HKLM\${PathToKey}" "ExecTime" "0000000000000000" "REG_QWORD" $R0
</highlight-nsis>

[[Category:Plugins]]
[[Category:INI, CSV & Registry Functions]]

ExecDos plug-in

2015-10-30T18:10:15Z

Faph: conda execute links

{{PageAuthor|Takhir}}

== Links ==
Download: 
<attach>ExecDos.zip</attach> 
[http://forums.winamp.com/showthread.php?threadid=181442 Forum thread]

Run with <code>conda execute</code> or install with <code>conda install</code> (see [[Conda]]).

== Description ==
Plug-in works with console applications - creates hidden child process with redirected i/o. Compared to nsExec, ExecDos has four add-ons:
# string parameter that serves as stdin for running application - may be useful if you want to give login/password to running application;
# sync/async (background) process launch option - async is good for long running applications;
# it works out of section - for .onInit check outs;
# multithreading - allows to run a few applications at the same time.
Plug-in can put application output to log file, 'detailed' installer window, any other text window, to installer stack or calls script function to handle every line. Maximum input (stdin) string size (i.e. plug-in second parameter) is up to 8 kB in the special NSIS build, 1 kB otherwise. The same with output lines length if target is not a file. 
'exec' return code depends on the execution mode: application exit code for sync mode and control thread handle for async one. Handle required for 'wait' - it helps to understand what application exit to wait for. If stack is not used between 'exec' and 'wait', both Pop after 'exec' and 'wait' parameter may be skipped - handle just sits in the stack.

ExecDos is licensed under the same license as NSIS; ZLIB. [http://forums.winamp.com/showthread.php?postid=2488873#post2488873]

== Syntax ==
=== "exec" function ===
<highlight-nsis>
ExecDos::exec [/NOUNLOAD /ASYNC] [/TOSTACK | /DETAILED | /TOWINDOW | /TOFUNC | /DISABLEFSR] [/TIMEOUT=xxx] \
[/ENDFUNC=func] application_to_run [stdin_string] [log_file_name | window | function]
</highlight-nsis>
: Executes console application.
; ASYNC
: does not wait for process to exit. Use 'wait' call if you want to get exit code. (/NOUNLOAD is mandatory!)
; TIMEOUT
: TOTAL execution time, milliseconds, for example /TIMEOUT=10000. Default is big enough. Short timeouts may cause app to be terminated.
; TOSTACK
: pushes output to stack instead of log_file (do not use log_file_name parameter with this option). May be confusing if few apps puts lines to stack in the async mode.
; DETAILED
: puts output to installer DetailedView window.
; TOWINDOW
: adds output lines to target window. Edit, RichEdit, ListView and ListBox supported
; TOFUNC
: pushes output lines to installer stack and calls script function
; DISABLEFSR
: Added /DISABLEFSR switch to disable WOW64 file system redirection on Windows x64 for the internal ExecDos thread
; application_to_run
: application to run.
; stdin_string
: all that application can get from stdin (optional, use "" if stack is not empty)
; log_file_name
: file where to put app's stdout (optional, but use "" if stack is not empty)
; window
: output window handle
; function
: script function pointer

=== "wait" function ===
<highlight-nsis>ExecDos::wait handle</highlight-nsis>
: Waits for process exit.
; handle
: Control thread handle returned by 'exec' call in the /ASYNC mode.

=== "isdone" function ===
<highlight-nsis>ExecDos::isdone /NOUNLOAD handle</highlight-nsis>
: checks thread is running. Returns 1 if application have exited, 0 if still running, -1 on error. /ASYNC mode only.
; handle
: Control thread handle returned by 'exec' call.

== Example ==
Sync execution:
<highlight-nsis>
ExecDos::exec /TIMEOUT=2000 "$EXEDIR\consApp.exe" "test_login$\ntest_pwd$\n" "$EXEDIR\execdos.log"
Pop $0 # return value
MessageBox MB_OK "Exit code $0"
</highlight-nsis>

Async execution:
<highlight-nsis>
ExecDos::exec /NOUNLOAD /ASYNC "$EXEDIR\consApp.exe" "test_login$\ntest_pwd$\n" "$EXEDIR\execdos.log"
Pop $0 # thread handle for wait
# you can add some installation code here to execute while application is running.
ExecDos::wait $0
Pop $0 # return value
MessageBox MB_OK "Exit code $0"
</highlight-nsis>

'''/TOSTACK'''
<highlight-nsis>
Push "ExecDos::End" # Add a marker for the loop to test for.
ExecDos::exec /NOUNLOAD /TOSTACK "$EXEDIR\consApp.exe" "test_login$\ntest_pwd$\n" "$EXEDIR\execdos.log"
Pop $0 # return value
StrCmp $0 0 0 Failed
## Loop through stack.
Loop:
Pop $1
StrCmp $1 "ExecDos::End" ExitLoop
DetailPrint $1
Goto Loop
ExitLoop:
Return # Exit Function / Section
Failed:
MessageBox MB_OK "Exit code $0"
Return # Exit Function / Section
</highlight-nsis>

'''/TOFUNC'''
<highlight-nsis>
Function OutputToLog
#Log the Output into the nsis logfile
LogText "$0"
Pop $0
FunctionEnd

Section -Core SEC0000
LogSet on
#Get the Address of the function
GetFunctionAddress $R2 OutputToLog

#Install Service
ExecDos::exec /TOFUNC '"$WINDIR\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe" "$INSTDIR\Core.exe"' '' $R2
SectionEnd
</highlight-nsis>

'''BAT files specifics.''' On some of Win98 systems where "Close on exit" option is not set for DOS apps it was found that after '''batch''' execution was finished (and installer continue it's job) hidden window still remains in the system as "winoldapp". Following two lines solve the problem
<pre>
@echo off
# place your code here
cls
</pre>
'''Telnet and ssh''' Plug-in doesn't work with applications requiring terminal emulation.

/TOFUNC option and isdone function added by Afrow UK

[[Category:Plugins]]

User:Faph

2015-10-30T17:57:34Z

Faph: Created page with "https://github.com/faph"

https://github.com/faph

Conda

2015-10-23T10:05:10Z

Faph: /* Option 1: Using conda execute */

{{PageAuthor|Faph}}

== What is Conda? ==

[http://conda.pydata.org Conda] is a cross-language package and environment manager. It can be used to install NSIS itself and various plugins and header files.

== Why use Conda for building NSIS installers? ==

Conda is particularly good at managing packages and installing required packages and its dependencies. NSIS plugins and macro header files can be distributed as conda packages. A repository of NSIS conda packages is available at [https://anaconda.org/nsis the anaconda.org NSIS channel].

Conda typically runs scripts in isolated environments. Configuring continuous integration or build servers is straightforward.

== How to use Conda ==

There are two possible approaches for building NSIS installers with conda:

# Using 'conda execute'
# Creating conda environments manually

=== Option 1: Using conda execute ===

Add this to the top of an NSIS source file:

<highlight-nsis>
# conda execute
# env:
# - nsis 3.*
# - plugin1
# - plugin2
# - ...
# channels:
# - nsis
# run_with: makensis

; NSIS source as usual ...
</highlight-nsis>

Then compile the file like this:

<pre>conda execute yourinstaller.nsi</pre>

This will create a temporary isolated conda environment with NSIS and the listed plugins installed. You don't need to have NSIS installed first! Then it simply runs <code>makensis</code> as usual.

Install [http://conda.pydata.org/miniconda.html miniconda] and [https://anaconda.org/conda-forge/conda-execute conda execute] first.

=== Option 2: Creating conda environments manually ===

Create a permanent NSIS environment like this:

<pre>conda create --name nsisenv --channel nsis nsis=3.* plugin1 plugin2 ...</pre>

Then run <code>makensis</code> within that environment to compile an NSIS source file.

This only requires [http://conda.pydata.org/miniconda.html miniconda].

== Creating Conda packages for NSIS plugins ==

It’s quite simple to create a "conda recipe" to build packages for NSIS plugins or header files. Just have a look at the examples in [https://github.com/faph/NSIS-Conda-Recipes this GitHub repo] and create a pull request with a new recipe. Once merged into the repo, the recipe will be built and the package published in the [https://anaconda.org/nsis anaconda.org NSIS channel].

Alternatively, raise a GitHub issue and someone may be willing to create a recipe.

[[Category:Development Environments]]

Conda

2015-10-20T08:45:59Z

Faph: /* How to use Conda */

{{PageAuthor|Faph}}

== What is Conda? ==

[http://conda.pydata.org Conda] is a cross-language package and environment manager. It can be used to install NSIS itself and various plugins and header files.

== Why use Conda for building NSIS installers? ==

Conda is particularly good at managing packages and installing required packages and its dependencies. NSIS plugins and macro header files can be distributed as conda packages. A repository of NSIS conda packages is available at [https://anaconda.org/nsis the anaconda.org NSIS channel].

Conda typically runs scripts in isolated environments. Configuring continuous integration or build servers is straightforward.

== How to use Conda ==

There are two possible approaches for building NSIS installers with conda:

# Using 'conda execute'
# Creating conda environments manually

=== Option 1: Using conda execute ===

Add this to the top of an NSIS source file:

<highlight-nsis>
# conda execute
# env:
# - nsis 3.*
# - plugin1
# - plugin2
# - ...
# channels:
# - nsis
# run_with: ./makensis

; NSIS source as usual ...
</highlight-nsis>

Then compile the file like this:

<pre>conda execute yourinstaller.nsi</pre>

This will create a temporary isolated conda environment with NSIS and the listed plugins installed. You don't need to have NSIS installed first! Then it simply runs <code>makensis</code> as usual.

Install [http://conda.pydata.org/miniconda.html miniconda] and [https://anaconda.org/conda-forge/conda-execute conda execute] first.

=== Option 2: Creating conda environments manually ===

Create a permanent NSIS environment like this:

<pre>conda create --name nsisenv --channel nsis nsis=3.* plugin1 plugin2 ...</pre>

Then run <code>makensis</code> within that environment to compile an NSIS source file.

This only requires [http://conda.pydata.org/miniconda.html miniconda].

== Creating Conda packages for NSIS plugins ==

It’s quite simple to create a "conda recipe" to build packages for NSIS plugins or header files. Just have a look at the examples in [https://github.com/faph/NSIS-Conda-Recipes this GitHub repo] and create a pull request with a new recipe. Once merged into the repo, the recipe will be built and the package published in the [https://anaconda.org/nsis anaconda.org NSIS channel].

Alternatively, raise a GitHub issue and someone may be willing to create a recipe.

[[Category:Development Environments]]

Conda

2015-10-20T08:39:09Z

Faph:

Conda

2015-10-19T19:39:05Z

Faph: /* Option 2: Creating conda environments manually */

Conda

2015-10-19T19:38:23Z

Faph: /* Option 1: Using conda execute */

{{PageAuthor|Faph}}

== What is Conda? ==

[http://conda.pydata.org Conda] is a cross-language package and environment manager. It can be used to install NSIS itself and various plugins and header files.

== Why use Conda for building NSIS installers? ==

Conda is particularly good at managing packages and installing required packages and its dependencies. NSIS plugins and macro header files can be distributed as conda packages. A repository of NSIS conda packages is available at [https://anaconda.org/nsis the anaconda.org NSIS channel].

Conda typically runs scripts in isolated environments. Configuring continuous integration or build servers is straightforward.

== How to use Conda ==

There are two possible approaches for building NSIS installers with conda:

# Using 'conda execute'
# Creating conda environments manually

=== Option 1: Using conda execute ===

Add this to the top of an NSIS source file:

<highlight-nsis>
# conda execute
# env:
# - nsis 3.*
# - plugin1
# - plugin2
# - ...
# channels:
# - nsis
# run_with: makensis

; NSIS source as usual ...
</highlight-nsis>

Then compile the file like this:

<pre>conda execute yourinstaller.nsi</pre>

This will create a temporary isolated conda environment with NSIS and the listed plugins installed. You don't need to have NSIS installed first! Then it simply runs <code>makensis</code> as usual.

Install [http://conda.pydata.org/miniconda.html miniconda] and [https://anaconda.org/conda-forge/conda-execute conda execute] first.

=== Option 2: Creating conda environments manually ===

Create a permanent NSIS environment like this:

<pre>conda create --name nsisenv --channel nsis nsis plugin1 plugin2 ...</pre>

Then run <code>makensis</code> within that environment to compile an NSIS source file.

This only requires [http://conda.pydata.org/miniconda.html miniconda].

== Creating Conda packages for NSIS plugins ==

It’s quite simple to create a "conda recipe" to build packages for NSIS plugins or header files. Just have a look at the examples in [https://github.com/faph/NSIS-Conda-Recipes this GitHub repo] and create a pull request with a new recipe. Once merged into the repo, the recipe will be built and the package published in the [https://anaconda.org/nsis anaconda.org NSIS channel].

Alternatively, raise a GitHub issue and someone may be willing to create a recipe.

[[Category:Development Environments]]

Conda

2015-10-19T18:51:44Z

Faph: /* Creating Conda packages for NSIS plugins */

{{PageAuthor|Faph}}

== What is Conda? ==

[http://conda.pydata.org Conda] is a cross-language package and environment manager. It can be used to install NSIS itself and various plugins and header files.

== Why use Conda for building NSIS installers? ==

Conda is particularly good at managing packages and installing required packages and its dependencies. NSIS plugins and macro header files can be distributed as conda packages. A repository of NSIS conda packages is available at [https://anaconda.org/nsis the anaconda.org NSIS channel].

Conda typically runs scripts in isolated environments. Configuring continuous integration or build servers is straightforward.

== How to use Conda ==

There are two possible approaches for building NSIS installers with conda:

# Using 'conda execute'
# Creating conda environments manually

=== Option 1: Using conda execute ===

Add this to the top of an NSIS source file:

<highlight-nsis>
# conda execute
# env:
# - nsis
# - plugin1
# - plugin2
# - ...
# channels:
# - nsis
# run_with: makensis

; NSIS source as usual ...
</highlight-nsis>

Then compile the file like this:

<pre>conda execute yourinstaller.nsi</pre>

This will create a temporary isolated conda environment with NSIS and the listed plugins installed. You don't need to have NSIS installed first! Then it simply runs <code>makensis</code> as usual.

Install [http://conda.pydata.org/miniconda.html miniconda] and [https://anaconda.org/conda-forge/conda-execute conda execute] first.

=== Option 2: Creating conda environments manually ===

Create a permanent NSIS environment like this:

<pre>conda create --name nsisenv --channel nsis nsis plugin1 plugin2 ...</pre>

Then run <code>makensis</code> within that environment to compile an NSIS source file.

This only requires [http://conda.pydata.org/miniconda.html miniconda].

== Creating Conda packages for NSIS plugins ==

It’s quite simple to create a "conda recipe" to build packages for NSIS plugins or header files. Just have a look at the examples in [https://github.com/faph/NSIS-Conda-Recipes this GitHub repo] and create a pull request with a new recipe. Once merged into the repo, the recipe will be built and the package published in the [https://anaconda.org/nsis anaconda.org NSIS channel].

Alternatively, raise a GitHub issue and someone may be willing to create a recipe.

[[Category:Development Environments]]

Conda

2015-10-19T18:49:21Z

Faph:

{{PageAuthor|Faph}}

== What is Conda? ==

[http://conda.pydata.org Conda] is a cross-language package and environment manager. It can be used to install NSIS itself and various plugins and header files.

== Why use Conda for building NSIS installers? ==

Conda is particularly good at managing packages and installing required packages and its dependencies. NSIS plugins and macro header files can be distributed as conda packages. A repository of NSIS conda packages is available at [https://anaconda.org/nsis the anaconda.org NSIS channel].

Conda typically runs scripts in isolated environments. Configuring continuous integration or build servers is straightforward.

== How to use Conda ==

There are two possible approaches for building NSIS installers with conda:

# Using 'conda execute'
# Creating conda environments manually

=== Option 1: Using conda execute ===

Add this to the top of an NSIS source file:

<highlight-nsis>
# conda execute
# env:
# - nsis
# - plugin1
# - plugin2
# - ...
# channels:
# - nsis
# run_with: makensis

; NSIS source as usual ...
</highlight-nsis>

Then compile the file like this:

<pre>conda execute yourinstaller.nsi</pre>

This will create a temporary isolated conda environment with NSIS and the listed plugins installed. You don't need to have NSIS installed first! Then it simply runs <code>makensis</code> as usual.

Install [http://conda.pydata.org/miniconda.html miniconda] and [https://anaconda.org/conda-forge/conda-execute conda execute] first.

=== Option 2: Creating conda environments manually ===

Create a permanent NSIS environment like this:

<pre>conda create --name nsisenv --channel nsis nsis plugin1 plugin2 ...</pre>

Then run <code>makensis</code> within that environment to compile an NSIS source file.

This only requires [http://conda.pydata.org/miniconda.html miniconda].

== Creating Conda packages for NSIS plugins ==

It’s quite simple to create a "conda recipe" to build packages for NSIS plugins or header files. Just have a look at the examples at [https://github.com/faph/NSIS-Conda-Recipes this GitHub repo] and create a pull request with a new recipe. We will build the recipe and publish it on the anaconda.org NSIS channel.

Alternatively, raise a GitHub issue and someone may be willing to create a recipe.

[[Category:Development Environments]]

Conda

2015-10-18T15:34:00Z

Faph: /* Option 2: Creating conda environments manually */

{{PageAuthor|Faph}}

== What is Conda? ==

[http://conda.pydata.org Conda] is a cross-language package and environment manager. It can be used to install NSIS itself and various plugins and header files.

== Why use Conda for building NSIS installers? ==

Conda is particularly good at managing packages and installing required packages and its dependencies. NSIS plugins and macro header files can be distributed as conda packages. A repository of NSIS conda packages is available at [https://anaconda.org/nsis the anaconda.org NSIS channel].

Conda typically runs scripts in isolated environments. Configuring continuous integration or build servers is straightforward.

== How to use Conda ==

There are two possible approaches for building NSIS installers with conda:

# Using 'conda execute'
# Creating conda environments manually

=== Option 1: Using conda execute ===

Add this to the top of an NSIS source file:

<highlight-nsis>
# conda execute
# env:
# - nsis
# - plugin1
# - plugin2
# - ...
# channels:
# - nsis
# run_with: makensis

; NSIS source as usual ...
</highlight-nsis>

Then compile the file like this:

<pre>conda execute yourinstaller.nsi</pre>

This will create a temporary isolated conda environment with NSIS and the listed plugins installed. You don't need to have NSIS installed first! Then it simply runs <code>makensis</code> as usual.

Install [http://conda.pydata.org/miniconda.html miniconda] and [https://anaconda.org/conda-forge/conda-execute conda execute] first.

=== Option 2: Creating conda environments manually ===

Create a permanent NSIS environment like this:

<pre>conda create --name nsisenv --channel nsis nsis plugin1 plugin2 ...</pre>

Then run <code>makensis</code> within that environment to compile an NSIS source file.

This only requires [http://conda.pydata.org/miniconda.html miniconda].

[[Category:Development Environments]]

Conda

2015-10-18T15:30:16Z

Faph: /* How to use Conda */

{{PageAuthor|Faph}}

== What is Conda? ==

[http://conda.pydata.org Conda] is a cross-language package and environment manager. It can be used to install NSIS itself and various plugins and header files.

== Why use Conda for building NSIS installers? ==

Conda is particularly good at managing packages and installing required packages and its dependencies. NSIS plugins and macro header files can be distributed as conda packages. A repository of NSIS conda packages is available at [https://anaconda.org/nsis the anaconda.org NSIS channel].

Conda typically runs scripts in isolated environments. Configuring continuous integration or build servers is straightforward.

== How to use Conda ==

There are two possible approaches for building NSIS installers with conda:

# Using 'conda execute'
# Creating conda environments manually

=== Option 1: Using conda execute ===

Add this to the top of an NSIS source file:

<highlight-nsis>
# conda execute
# env:
# - nsis
# - plugin1
# - plugin2
# - ...
# channels:
# - nsis
# run_with: makensis

; NSIS source as usual ...
</highlight-nsis>

Then compile the file like this:

<pre>conda execute yourinstaller.nsi</pre>

This will create a temporary isolated conda environment with NSIS and the listed plugins installed. You don't need to have NSIS installed first! Then it simply runs <code>makensis</code> as usual.

Install [http://conda.pydata.org/miniconda.html miniconda] and [https://anaconda.org/conda-forge/conda-execute conda execute] first.

=== Option 2: Creating conda environments manually ===

Create a permanent NSIS environment like this:

<pre>conda create -n nsisenv -c nsis nsis plugin1 plugin2 ...</pre>

Then run <code>makensis</code> within that environment to compile an NSIS source file.

This only requires [http://conda.pydata.org/miniconda.html miniconda].

[[Category:Development Environments]]

Conda

2015-10-18T15:13:46Z

Faph:

Conda

2015-10-17T21:13:35Z

Faph:

{{PageAuthor|Faph}}

The [http://conda.pydata.org conda package and environment manager] can be used to install NSIS, plugins and header files.

There are two possible approaches:

# Using 'conda execute'
# Creating conda environments manually

== Using conda execute ==

Add this to the top of an NSIS source file:

<highlight-nsis>
# conda execute
# env:
# - nsis
# - plugin1
# - plugin2
# channels:
# - nsis
# run_with: makensis
</highlight-nsis>

Then compile the file like this:

<pre>conda execute yourinstaller.nsi</pre>

This will create a temporary isolated conda environment with NSIS and the listed plugins installed. You don't need to have NSIS installed first! Then it simply runs <code>makensis</code> as usual.

You will need to install [http://conda.pydata.org/miniconda.html miniconda] (or the full blown [https://www.continuum.io/anaconda anaconda] first and then [https://anaconda.org/conda-forge/conda-execute conda execute].

== Creating conda environments manually ==

TODO

[[Category:Development Environments]]

Conda

2015-10-17T21:05:36Z

Faph:

{{PageAuthor|Faph}}

The [http://conda.pydata.org conda package and environment manager] can be used to install NSIS, plugins and header files.

There are two approaches:

# Using 'conda execute'
# Creating conda environments manually

== Using conda execute ==

Add this to the top of an NSIS source file:

<highlight-nsis>
# conda execute
# env:
# - nsis
# - plugin1
# - plugin2
# channels:
# - nsis
# run_with: makensis
</highlight-nsis>

Then compile the installer like this:

<pre>conda execute yourinstaller.nsi</pre>

This will create a temporary isolated conda environment with NSIS and the listed plugins installed. You don't need to have NSIS installed first! Then it simply runs makensis as usual.

== Creating conda environments manually ==

TODO

[[Category:Development Environments]]

Conda

2015-10-17T20:58:02Z

Faph: Created page with "The conda package manager can be used to install NSIS, plugins and header files. There are two approaches: # Use conda execute # Create conda environments manually == Using..."

The conda package manager can be used to install NSIS, plugins and header files.

There are two approaches:

# Use conda execute
# Create conda environments manually

== Using conda execute ==

Add this to the top of an NSIS source file:

<highlight-nsis>
# conda execute
# env:
# - nsis
# - plugin1
# - plugin2
# channels:
# - nsis
# run_with: makensis
</highlight-nsis>

Then compile the installer like this:

<pre>conda execute yourinstaller.nsi</pre>

This will create a temporary isolated conda environment with NSIS and the listed plugins installed. You don't need to have NSIS installed first! Then it simply runs makensis as usual.

== Creating conda environments manually ==

TODO

[[Category:Development Environments]]