News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

Using NSIS under C::B

Started by idcarlos, March 09, 2006, 04:39:59 PM

Previous topic - Next topic
Print
Go Down Pages1
User actions

idcarlos

March 09, 2006, 04:39:59 PM
Mini HOWTO about using NSIS under C::B

1.- Donwload and intall NSIS lexer (http://forums.next.codeblocks.org/index.php?topic=2549.0)
2.- Open a .nsi file under C::B. Now you must see the code highlited
3.- Go to tools->Configure Tools->Add...
4.-Fill the Tools options

  • Put a descripcion like "NSIS Compiler"
  • The makensisw.exe path, you can use also makensis.exe bu it's hard to see the errors
  • Under Parameters, set "${ACTIVE_EDITOR_FILENAME}" (you need the "" for the long paths)
5.-Test it  :D

I'm looking the default.conf, maybe I can and Makesis as a compiler, but maybe not is a good idea because, as external tool works ok.

Any one can check my Spanglish and put this post in the Wiki?

Un saludo
Carlos Garces

killerbot

#1
March 09, 2006, 04:49:55 PM
thx, great information.

thomas

#2
March 09, 2006, 04:53:20 PM
Quote from: idcarlos on March 09, 2006, 04:39:59 PMI'm looking the default.conf, maybe I can and Makesis as a compiler, but maybe not is a good idea because, as external tool works ok.
Right now, it is a bad time to do that, better wait a while.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

idcarlos

#3
March 10, 2006, 09:14:58 AM
Quote from: thomas on March 09, 2006, 04:53:20 PM
Quote from: idcarlos on March 09, 2006, 04:39:59 PMI'm looking the default.conf, maybe I can and Makesis as a compiler, but maybe not is a good idea because, as external tool works ok.
Right now, it is a bad time to do that, better wait a while.
Hi.

One problem that I found it is when the external tool is a command line tool. The cmd is closed and you can see anything.
I can fix it using a .bat file with @pause command but...

What do you think about and one check in the Tools Options dialog, to close (or not) the external window?

takeshimiya

#4
March 10, 2006, 09:40:14 AM
Quote from: idcarlos on March 10, 2006, 09:14:58 AM
What do you think about and one check in the Tools Options dialog, to close (or not) the external window?
aka a checkbox to toggle running console_runner. :P

mandrav

#5
March 10, 2006, 10:27:24 AM
Quote from: SVN commit log
* Tools' output is now logged.
* Another option was added for tools: "launch in a console and wait for keypress". Note that with this option, the tool's output is not logged.
Be patient!
This bug will be fixed soon...

idcarlos

#6
March 10, 2006, 05:37:45 PM
Quote from: mandrav on March 10, 2006, 10:27:24 AM
Quote from: SVN commit log
* Tools' output is now logged.
* Another option was added for tools: "launch in a console and wait for keypress". Note that with this option, the tool's output is not logged.

Sorry...

This is a future featuee or a feature in a nigthy build that I can't find?

killerbot

#7
March 10, 2006, 05:41:25 PM
tonight's nightly !!!

idcarlos

#8
March 10, 2006, 05:55:57 PM
Quote from: killerbot on March 10, 2006, 05:41:25 PM
tonight's nightly !!!
:lol:
Development is too fast for me!
The C::B developers can add the features faster than users request  :lol:
Print
Go Up Pages1
User actions