I have a portable app (Eclipse Portable) that spawns a compiler (iverilog.exe). However, the compiler--which is installed under the portable app's folder--requires DLLs. I can make the compiler run by copying the DLLs to the Windows\System32 folder on the host machine. Of course, this makes the PortableApp no longer portable.
Does anyone know how to setup the PortableApp to locate the DLLs? Or configure the environment variables?
I have searched and searched the forums but the closest I can get to an answer to my question is the post titled "Converting Normal Applications to portable ones" by Ww2nerd - March 13, 2008 - 1:50pm.
AFAICT, putting the DLLs in the same folder as iverilog.exe should work
"Der Klügere gibt nach, deshalb regieren Dumme die Welt."
Thanks for your suggestion.
However, the DLLs were already in the same folder as iverilog.exe. Below is my folder structure of my PortableApp:
I tried again anyway with the DLLs placed in the bin, iverilog, Eclipse, App, and EclipsePortable folders. However, iverilog.exe still will not run. What am I missing?
Can you set the working directory of the compiler? It should be enough to make Windows happy.
Previously known as kAlug.
No, I was not able to set the working directory -- because the UI does not give me access. However, I did find a directory on the PortableApp where the compiler was actually looking. It now compiles fine with the DLLs installed in the right directory. Now I just need to find a more elegant way to access the DLLs without having to move them around. Thanks.
Is that the same Eclipse as this one already being developed?
“Be who you are and say what you feel because those who mind don't matter and those who matter don't mind.” Dr. Seuss
Yes - it is the same. I installed the Eclipse Portable, Classic Edition. Then I installed plug-ins for veditor, Wascana (CDT), and JDT through Eclipse's install portal. The plug-ins work except that I have to set Eclipse to use the JRE on the PortableApp and not on the desktop.
For ordinary DLLs, put the path to them in the PATH.
For side-by-side assemblies, panic. (There are ways of doing it but it's a slight pain.)
Try the former; what are the DLLs?
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
The DLLs are "libgcc_s_dw2-1.dll" and "libstdc++-6.dll". Placing the DLLs in the right directory or setting the PATH of the host computer works. How do I set the PATH through the PortableApp?
Is this what you need: http://portableapps.chrismorgan.info/launcher/manual/ref/launcher.ini/en...
MJA
Thanks, this appears to be exactly what I need.
I have some questions though.
Given my directory structure:
After reading through the manual, I created the folder named Launcher under AppInfo. Then I created a file named EclipsePortable.ini with the following contents:
[Environment]
PATH=%PATH%;%PAL:AppDir%\Eclipse
APPNAME_HOME=%PAL:DataDir%\settings
Am I on the right track? Should I expect to see both "X:\PortableApps\EclipsePortable\App\Eclipse" and "X:\PortableApps\EclipsePortable\Data\settings" on the PATH after launching PortableApps launcher?
Yes, you seem to be getting there. I'm not familiar with the App you are working on and am still working my way through a variety of different apps to build my own understanding so you probably need some more knowledgeable input. - Java dependent apps still remain something of a mystery to me!
My Questions:
1. Do you really need a Java Directory in your structure? Are you not using JPortable? Or, is it because you want your app to be able to work completely independently of the PortableApps Platform?
2. Have you checked out the Eclipse Development Test Builds here - https://portableapps.com/node/22236 for any pointers towards what you are trying to achieve? Perhaps Gluxon would help if you posted a query on that thread.
Best of luck.
MJA
Answers 1 & 2 (combined): I am using one of the Eclipse Development Test Builds. The build contains the Java folder you were looking at. The C++ and Java Development tools work fine in my build. Just having problems with an Eclipse plugin that requires a different type of compiler.