executable

Is there a way to determine if the current file is the one being executed in Perl source? In Python we do this with the following construct: if __name__ == '__main__': # This file is being executed. raise NotImplementedError I can hack something together using FindBin and __FILE__ , but I'm hoping there's a canonical way of doing this. Thanks! unless (caller) { print "This is the script being executed\n"; } See caller . It returns undef in the main script. Note that that doesn't work inside a subroutine, only in top-level code. Chas. Owens See the "Subclasses for Applications (Chapter 18)"

I'm using PyInstaller to create a single executable of a python program using PyQt. It creates the .exe and runs fine, but takes between 15 to 20 seconds to start. I thought I could get by with creating a splash screen so the user would at least know something was happening, unfortunately, the splash screen doesn't show up any quicker than the program window itself. I also created the same program as -onedir, the program does start quicker, but this isn't really an option for distribution. If anyone has any ideas on what is slowing down the execution and ways to speed things up I would

When I call an external .exe program in Python, how can I get printf output from the .exe application and print it to my Python IDE? gimel To call an external program from Python, use the subprocess module. The subprocess module allows you to spawn new processes, connect to their input/output/error pipes, and obtain their return codes. An example from the doc ( output is a file object that provides output from the child process.): output = subprocess.Popen(["mycmd", "myarg"], stdout=subprocess.PIPE).communicate()[0] A concrete example, using cmd , the Windows command line interpreter with 2

I'm on a Windows machine using Git 2.7.2.windows.1 with MinGW 64. I have a script in C:/path/to/scripts/myScript.sh . How do I execute this script from my Git Bash instance? It was possible to add it to the .bashrc file and then just execute the entire bashrc file. But I want to add the script to a separate file and execute it from there. Let's say you have a script script.sh . To run it ( using Git Bash ), you do the following chmod +x script.sh ./script.sh You can change the chmod to the executable permissions that you want. Those can be found here . Note: The chmod only has to be run once .

I am distributing a Java program where I want a double-clickable file to run java -cp MyProgram.jar;MyLib.jar my.program.Main On Windows I simply distribute a .bat file, for *nix an executable .sh file. Problem is, double-clicking the .sh file just opens it up in a text editor on Mac. What should I do for Mac? On mac, there is a specific extension for executing shell scripts by double clicking them: this is .command . For Java applications on Mac, you really should use Apple's Jar Bundler (in the Developer Tools/Applications/Utilities folder; really a symlink to /usr/share/java/Tools/Jar

Richard of Last.fm over at metabrew has ported his apps to Erlang . It was also done by riak, couchdb and others. He mentions extracting the needed parts, or including the whole VM into the distribution. Main trait here is: the program does not require Erlang to be installed on the target machine. So the question is, how do you, step by step, package an Erlang program into a windows (and, less important, linux) executable? P.S. I've seen the SAE project, and I've read all the relevant questions here. None answer my question. Create a portable version of Erlang (for example using method from

What happens if I recompile an executable while it's running? Does the operating system read all of the executable's contents into memory when it starts running it, so it will never read the new executable file? Or will it read sections of the new executable file thinking it hasn't changed, leading to possibly undefined behaviour? What if I have a script running which repeatedly invokes an executable in a loop, and I recompile the executable while the script is running. Is it guaranteed that future iterations of the loop will invoke the new executable, and only the result of the invocation