且构网

分享程序员开发的那些事...
且构网 - 分享程序员编程开发的那些事

合并不同的应用程序

更新时间:2022-11-06 14:57:31

首先,这不是一个C ++问题,它甚至不是编程问题 - 这是关于自动化安装。 b / b


其次,您需要拥有所需的许可证,许可证必须允许您按照您描述的方式复制软件。请注意,某些软件(如VS2008)可能附带的安装介质仅对单个安装有效,并且可能无法合法地复制到多个设备。



三,标准安装程序软件可能并不总是有用,因为某些软件(如VisualStudio)必须运行自己的安装程序才能正确安装,有些可能需要重启!



最简单的方法将收集每个程序的安装文件放在不同的目录中,并编写一个简单调用安装程序exe文件的批处理文件或简单的GUI程序。您需要检查是否可以在不重新启动的情况下安装所有程序,并且需要找到安装的工作顺序。



另一种方式是检查安装程序(例如解决方案1中发布的程序)并找出它们是否支持这种安装过程。



通常的方法是写一个项目手册,描述了需要安装的软件工具,在何处查找安装文件,安装顺序,请求进一步指导的人员,以及常用设置和命令列表。然后让每个程序员自己完成。


在Visual Studio中,创建一个MSI项目。



http://msdn.microsoft.com/en-us/library/cc185688%28v=vs .85%29.aspx [ ^ ]



或者使用像NSIS这样的工具包。



http://nsis.sourceforge.net/Main_Page [ ^ ]



第三种方法是自行解压缩自安装程序。



自解压安装程序 [ ^

how do we merge different softwares like vs2008, some gui applications(Qt) together along with the required drivers to combine and form one application where user does next and it gets installed auotomatically one aftr d other by giving the command next as software is installed

First, this is not a C++ question, it is not even a programming question - this is about automating installations.

Second, you need to own the required licenses and the licenses must allow you to copy the software in the way you describe. Note that some software such as VS2008 may come with installation media that are valid only for a single installation and may not legally be copied to multiple devices.

Third, standard Installer software may not always help, since some software (such as VisualStudio) must run their own installer program to be properly installed, and some may require rebooting!

The easiest way would be to gather the installation files for each program in separate directories, and write a batch file or simple GUI program that simply calls the installer exe files. You'll need to check if it is possible to install all programs without rebooting in between, and you need to find a working order of installation.

Another way would be to check out installer programs (such as the ones posted in solution 1) and find out whether they suport this kind of installation process.

The usual way is to write a project handbook that describes the software tools that need to be installed, where to find the installation files, the order of installation, who to ask for further guidance, and maybe a list of commonly used settings and commands. Then let each programmer do it by themselves.


In Visual Studio, create an MSI project.

http://msdn.microsoft.com/en-us/library/cc185688%28v=vs.85%29.aspx[^]

Or use a toolkit like NSIS.

http://nsis.sourceforge.net/Main_Page[^]

A third approach is a roll-your-own self extracting installer.

A Self-extracting Installer[^]