executable

How to package executable JAR file into EXE

由 生来就可爱ヽ(ⅴ＜●) 提交于 2019-11-30 08:17:16
问题 I would like to deploy my final build as an EXE with an application Icon. What is the best way to do this? What is the common practice? 回答1: Launch4j is a cross-platform tool for wrapping Java applications distributed as jars in lightweight Windows native executables. The executable can be configured to search for a certain JRE version or use a bundled one, and it's possible to set runtime options, like the initial/max heap size. The wrapper also provides better user experience through an

Create single python executable module

由 ∥☆過路亽．° 提交于 2019-11-30 07:39:34
Guys, I have much python code in modules which are resides in several python packages and now I need to create single python executable module or file which will include all these files, so it will be working on windows and on linux servers. What are possible solutions and how this can be done? S.Lott That's what egg files are for. Read this: What are the advantages of packaging your python library/application as an .egg file? For windows use py2exe , for linux use pyinstaller and for Mac use py2app Using these tools you can have a setup.py which based on os will build the final binary. I have

Determining Which Compiler Built a Win32 PE

由 家住魔仙堡 提交于 2019-11-30 07:03:45
How can one determine which C or C++ compiler was used to build a particular Windows executable or DLL? Some compilers leave behind version strings in the final executable, but this seems to be rarer on Windows than on Linux. Specifically, I'm interested in distinguishing between Visual C++ and the various MinGW compilers (usually fairly easy from the function signatures), and then between Visual C++ versions (6, 2002/2003, 2005, 2008; more difficult to do). Is there a tool out there that can make the distinction in a semi-reliable way? One source of a hint to distinguish among VC versions is

Exec format error 32-bit executable Windows Subsystem for Linux?

由 大兔子大兔子 提交于 2019-11-30 05:53:46
问题 When I try to execute a 32-bit file compiled with gcc -m32 main.c -o main on Windows Subsystem for Linux , I get the following error: bash: ./main: cannot execute binary file: Exec format error . If I compile it without -m32 it runs. Any solution for running 32-bit executable on WSL ? 回答1: 32-bit ELF support isn't provided by WSL (yet). There doesn't seem to be any progress since the UserVoice was raised - you are out luck. See UserVoice: Please add 32 bit ELF support to the kernel and

Launching an executable from a website?

由 梦想的初衷 提交于 2019-11-30 05:28:39
We're developing a site that will only run on the intranet, and computers with access to this intranet will have this executable installed. We can't have any "Would you like to open [filename].exe?" prompts. Click a link and the program begins running. I realize that giving websites the ability to run executables on the client machine is very, very bad, but management refuses to budge on this. Machines will have Windows (XP or up) with Firefox 3. We're developing a site that will only run on the intranet, and computers with access to this intranet will have this executable installed. Does this

Creating executable for Windows using Qt on Linux

由 冷暖自知 提交于 2019-11-30 05:15:11
问题 Is it possible to create an executable on Linux for both Linux and Windows using the same Qt code with Eclipse? Or is it necessary to install Qt Creator on my Linux machine? 回答1: If you want to build a windows binary on linux you need to cross-compile. This means you need to have a windows cross-compiler installed plus the libraries you are linking with built with the cross compiler . For a basic Qt program this means you need at least a cross-compiled Qt. Cross-compiling has nothing to do

Windows Lua to executable

由 余生颓废 提交于 2019-11-30 05:09:13
问题 hi I have a Lua program (written in Lua 5.1). I'm on Windows 7, trying to convert it to an executable. No luck so far. I've read other posts here that suggested using srlua to do this so I've downloaded it but I'm on a loss as to what to do next. I installed cygwin as I understand it's necessary but I don't know how to use srlua to convert a lua file into an executable. Any help will be appreciated. 回答1: srlua is distributed as source only, so you have to compile it first (see this answer for

Determining C executable name

由 与世无争的帅哥 提交于 2019-11-30 04:43:58
When we are compiling a C program the output is stored in a.out. How can we redirect the compiled output to another file? Most C compilers provide the -o option for this, such as: gcc -o gentext gentext.c cc -o mainprog -Llib -lmymath firstbit.c secondbit.o xlc -o coredump coredump.c -ofilename will make filename instead of a.out . Arkaitz Jimenez According to the manual: -o <file> Place the output into <file> In Unix, where C originated from, C programs are usually compiled module-by-module, and then the compiled modules are linked into an executable. For a project that consists of modules

Dependency resolution in Linux

由 前提是你 提交于 2019-11-30 04:15:18
问题 Under Windows I have used a program called dependency walker to examine the libraries the application is using. I was wondering how I can achieve this on Linux for a standard binary: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.0, stripped Thanks. 回答1: Try: ldd executable For example: [me@somebox ~]$ ldd /bin/ls linux-gate.so.1 => (0xb7f57000) librt.so.1 => /lib/tls/i686/cmov/librt.so.1 (0xb7f4c000) libselinux.so.1 => /lib

One big executable or many small DLL's?

由 僤鯓⒐⒋嵵緔 提交于 2019-11-30 03:44:37
Over the years my application has grown from 1MB to 25MB and I expect it to grow further to 40, 50 MB. I don't use DLL's, but put everything in this one big executable. Having one big executable has certain advantages: Installing my application at the customer is really: copy and run. Upgrades can be easily zipped and sent to the customer There is no risk of having conflicting DLL's (where the customer has not version X of the EXE, but version Y of the DLL) The big disadvantage of the big EXE is that linking times seem to grow exponentially. Additional problem is that a part of the code (let's
订阅 executable