I wanna build a language patch which involves Xdelta. Right now I am able patch the original files via batch file but it requires Xdelta files and batch file to be fixed in the target directory.
What I am saying is: a setup that has functions of Xdelta would be convenient 'cause I wanna make it user-friendly and I don't want anyone else to see command lines written down as they install the patch. How can I build such a thing?
Related
I'm pretty sure this isn't how I'm supposed to use windeployqt, but I have an executable which is missing some dependencies (specifically the qt plugin windows). I thought I could use the windeployqt tool in order to find the missing dependencies for this executable and install them, but I get a "does not exist" error when I try and run the following:
windeployqt.exe ExecutableFileName.exe
I tried this after trying the full path (e.g. windeployqt.exe pathtoexecutablefile\executablefilename.exe
but both times I get two errors. Either filename.exe does not exist, or pathtofile\filename.exe doesn't exist. Is there a way to fix this or am I using the tool wrong? I've added the folder containing the tool to my system path, but do I need to add the folder containing the executable as well?
Problem
I see all these plugins from MobaXTerm, but I don't know how to make my own. I see no links to any tutorials or whatever. Is there even a way to do it?
What I really want (XY problem)
I want to create my own commands. I want these to be available on each server I go to and I don't want to add each of these to my bin and .bash_profile etc. I think plugin is the way to go.
Even more background
I am not that good in shell programming, but I can program java. I created a jar which handles my commands. So I have created my own linux script on my local environment to test all these things. They work, but I dont want to 'export' them to other servers. Seems like a bad idea to do.
MobaXterm plugins are just Windows or Cygwin executables packaged in a .mxt3 file which is just a standard ZIP archive with a specific structure.
Read this from the MobaXterm FAQ:
I would like to create a new plugin for MobaXterm. How can I do that?
Download an existing plugin file (for instance "Midnight commander")
Rename plugin extension from ".mxt3" to ".zip"
Open the ".zip" file You will notice that creating MobaXterm plugins only consists in putting the required commands (executables, libraries
and configuration files) into a ZIP file, keeping the same folders
tree than in MobaXterm ("/bin", "/lib", "/usr", "/etc").
If you want to add a simple Windows program (exe file), you will just have to copy the executable file into the "/bin" directory,
create the ZIP archive, rename it to ".mxt3" and put it in the same
directory than MobaXterm executable.
If you want to add a Linux program, you will have to get it from the Cygwin project or to recompile it using make, gcc, g++ or other
compilers that are available from the MobaXterm "Development" plugin.
Remember MobaXterm's terminal is just Cygwin, so you may be able to cross compile some packages within Moba by simply installing the necessary compiler tools.
I have a setupOriginal.exe file, and I would need to update it to had some features.
I can unzip it with 7Zip and it contains a hierarchy like that:
Autorun.inf
setup.exe
setup.exe.manifest
Directory\main.msi
As far as I know, the file setupOriginal.exe is some kind of auto extractable file since I can unzip it.
Once unzipped, I can modify the main.msi file.
But, I am not able to rebuild the packed setup.exe into one file setupAltered.exe which would run the same way as before, and contain the hierarchy:
Autorun.inf
setup.exe
setup.exe.manifest
Directory\mainAltered.msi
I tried:
to build self extractable with 7Zip and WinZip but there is an intermediate unzip step
to update setupOriginal.exe inline and save directly without unzipping in WinZip (a new exe is generated, but it is broken) and 7Zip (error message when adding mainAltered.msi "function not implemented")
I guess files are packed with a tool that forward the setup to the inner setup.exe, but I don't know it.
Do I need to use some kind of installer tools (InnoSetup etc.) to wrap the files ? In this case, how could I do it if I just want to pack the files, and run the setup.exe from inside the packed archive (I mean without introducing a intermediate window added by the installer tool itself) ?
Is there any simple way to do that please ?
Thanks,
To anymore interested, the best approach I found is to use WinZip Self-Extractor program (part of binaries created by WinZip, but different from the main WinZip program I tried to use for SFX, and that will not allow to tune options as far as I know).
You can request for automatic unzipping, set icon and run the inner setup.exe afterwards.
And, finally, it can be called from command line:
"C:\Program Files (x86)\WinZip Self-Extractor\WZIPSE32.EXE" test.zip -setup -t dialog.txt -auto -i icon.ico -c .\setup.exe
I have the .proto file used in the open-source Android API (http://code.google.com/p/android-market-api/), and am having some trouble compiling the file to generate the .py.
I'm trying to follow the instructions here, https://developers.google.com/protocol-buffers/docs/pythontutorial , and am on the steps that are under the header "Compiling Your Protocol Buffers".
I've downloaded the compiler, protoc.exe. The readme says "To install, simply place this binary somewhere in your PATH," which I'm not understanding. I'm messed around with it for a while now, but can't think of how to proceed.
I'm quite the novice programmer, so please tell me if something isn't clear, or if I'm having some sort of fundamental misunderstanding... about anything. I'm on Windows 7 by the way.
Thanks!
if protoc.exe is not in the same directory you're calling it from, you need to add it to your PATH environment variable to be accessible from the calling directory when you're in the shell. open up a command shell and execute:
set PATH=%PATH%c:\directory\to\proto\executable;
then change directories over to where your source code is and execute the compilation line as instructed from the google page.
I had the same problem because it is not written that clear in the README.txt. What they mean is to:
1. take the protoc.exe and put it in the same folder with the other files of your project.
2. open the cmd to that directory and run: protoc --cpp_out=. myfile.proto
=> This will create the 2 new files in the folder with the files of your project, and then you can add them normally to your program.
This helped me: http://www.scriptol.com/programming/protocol-buffers-tutorial.php
This is for c++, but I guess it will be something similar for python; I guess you just have to change the command you are using in the cmd :)
I'm trying to get Bison to do it's thing in VC6. I'm sure this must be a problem with my configuration. At the moment I have a Custom Build step as follows.
<Commands>
echo Start parser generation
"C:\GnuWin32\bin\bison.exe" $(InputPath)
echo Finish parser generation
<Outputs>
$(ProjDir)\$(InputName).c
$(ProjDir)\$(InputName).h
The error I get is "C:\GnuWin32\bin\bison.exe: m4: No such file or directory", which makes me think the m4.exe doesn't exist or isn't on the path, but I can run the exact same command from CMD in the same directory with no errors.
This thought process makes me think it's a problem with the output options, but I've tried various configurations with no luck.
Any help would be great, thanks in advance.
Edit: I've added some more visual studio versions to the tag list to try to get some more exposure for the question. Hopefully someone will have done this in a later version and I can work backwards.
Okay, I've managed to slove this in a very round-about way but I will try my best to document it here.
It seems that VC6 Custom build options will only look in the project directory for the m4.exe, even when you specify where the calling exe (bison) is explicitly. To solve this I did a bit of a hack and did a full cd command in the custom build window to get to the gnuwin32 directory (where both bison and m4 live) before trying to call the parser generator.
This works fine but is a bit of a hassle for trying to distribute it to other people when they may have installed GNU tools to a different location.