I created one package using NSIS but to install this package on any machine,it's asking for admin credentials. I tried to find out .nsi file for this created package to change RequestExecutionLevel but could not find that. Can anybody suggest where should I check for .nsi file that has been created for new package?
As far as I know NSIS should generate .nsi file for package created. Correct me if I'm wrong here.
NSIS itself does not create .nsi files, it expects you to write them yourself in your favorite editor. The only .nsi files provided by NSIS are in \NSIS\Examples.
A 3rd-party NSIS editor with a wizard feature might create a .nsi for you...
Related
I am trying to commit my SSIS package to Git and I'm running into an issue with adding the Script Component code files. I have my SSIS package within my Git repository location, but the code file is located in the AppData folder as such:
C:\Users\Jeremy\AppData\Local\Temp\Vsta\SSIS_SC110\Vstak5QLNZovpE__2Hp8ieeyROw\Vsta_luuBHnd9ka0dNruaTdUoQ\main.cs
I would like to add the entire SSIS package to Git so others can use the SSIS package on the team. Does anyone know how to add the "Script Component" files to the repository?
Hi this is the usual behavior of the Visual Studio. When you open up a script task it will be added to a temporary location. while opening it will go to a temporary location to edit.
Once you clean and build the application it will be available inside of the .dtsx package. You have to commit the entire project and for a new user who get a pull will get the code without any issue.
I'd like to open a .vhd and .vhi file in window for editing in Vivado from Tcl Console, but I can't find any command for that.
As of at least Vivado 2014.2 any unrecognized Tcl command will be sent to the OS shell for execution, so you can simply open whatever editor you like as if you were not in the Tcl shell. It basically automatically runs exec for you. Older versions you may have to run exec yourself.
eg
nedit file.vhd
Vivado being a design tool works on projects instead of individual files. So to edit a file, say xyz.vhd, the file needs to be part of a project. This can be done through Tcl console by creating a new project, adding xyz.vhd file to it and then loading the project.
Create a new project using the following command:
project -new
Add files:
add_file -vhd "xyz.vhd"
Save the project and run.
project -save
project -run
You can find further resources at this link.
I have created a .erl file named "confirmDelivery.erl" and compile it successfully, A beam file named "confirmDelivery.beam" has been created.
All these files are in /etc/ejabberd/. Now I wanna add the functionality of this file into ejabberd, But I don't know how to link my file with ejabberd server.
Please help me, I will be really really thankful to you.
You need to place your beam files in the path of the Erlang VM to be able to use them. You should have a look at where are other ejabberd module for example and place it in the same directory.
You need to put your beam file in etc/ejjaberd/ebin folder and call it from ejabberd debug mode.
use command:
ejabberdctl debug
i want to use my mysql databases in weka in order to analysis data.
i download the mysql-connector-java-5.0.8-bin.jar and put that in weka folder in my program Files folder, and add this path to system variable path, but when i open the weka explorer and click the openDB, i don't know what should i write in the url textbox,
i don't know completely what should i do?
the error that i saw is:
problem connecting to database:
no suitable driver found for!
please give me a total guidance, thanks in advance.
add mysql-connector-java-5.1.12-bin.jar to CLASSPATH .
or put it in weka folder, navigate to weka installation folder and run command :
%java_home%/bin/java -Xmx300M -cp ".;weka.jar;mysql-connector-java-5.1.12-bin.jar;" weka.gui.GUIChooser
then click open DB and
fill in the proper user+password
put the url: jdbc:mysql://localhost:3306/DATABASENAME
Click Execute. The result window should show the results now.
For Weka 3.7.10, the classpath system environment variable is not took into account (at leat under Windows 7). The only working approach for me was to modify the RunWeka.ini file from the Weka installation folder as follows: the cp= setting was modified to:
cp=%CLASSPATH%;d:/Programs/jdbc/mysql-connector-java-5.1.26/mysql-connector-java-5.1.26-bin.jar
whereas only the %CLASSPATH%; setting was originally provided. Does not make much sense, but in worked.
find some introduction to WEKA and the environment variable:
http://weka.wikispaces.com/CLASSPATH
Copy mysql-connector-java-X.X.XX-bin.jar to /usr/share/java/
unizip /usr/share/java/weka.jar
edit: /usr/share/java/weka/experiment/DatabaseUtils.props
add:
jdbcDriver=com.mysql.jdbc.Driver
jdbcURL=jdbc:mysql://localhost:3306/test (with your server)
add shell
export CLASSPATH=/usr/share/java/mysql-connector-java-X.X.XX-bin.jar:
export CP=/usr/share/java/mysql-connector-java-X.X.XX-bin.jar::/usr/share/java/:/usr/shared/java/weka.jar
execute weka:
java -cp $CP -Xmx500m weka.gui.explorer.Explorer
Ready
Is there a autoconf macro to configure generic library that can:
generates --with configure option
setup library and include path
setup compiler/preprocessor and linker flags
check existence of library and include files
setup configuration macros
Right now I am doing everything using ARG_WITH, CHECK_LIB, etc. the steps are generic and end up being copy/paste with minor changes. My search the macro archive and did not find generic solution.
Thanks
It's not the complete solution, but you might find AX_PATH_GENERIC from the Autoconf Macro Archive useful: http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=blob;f=m4/ax_path_generic.m4