We skip past the git.exe requirement and try to create a web project and guess what, yep - it' asks for firefox.exe. So we try to re-point it to Q:\Aptana.304\bin\git.exe, but the bin directory is now empty!? *ī. The client fires up Aptana and immediately it asks for GIT.exe. So we finish up and stream the virtualised Aptana and Git to the client.Ī. Still within Aptana we then create a new web project and it asks for the location of Firefox (for debugging puposes)s, so we point Aptana to Q:\firefox.501\firefox.exeWe then close Aptana, create another web project and it seems to work okay.Ħ. We then fire up AptanaStudio 3.0.4 whilst it's int he sequencer and it asks for the GIT.exe (We're presuming it's hardcoded to look in a particular directory?), so we point it to Q:\Aptana.304\bin\git.exeĥ.
Aptana for windows 7 64 bit install#
After the files extract we run the AptanaStudio 3.0.4 install and also install this to Q:\Aptana.304Ĥ. We installed the pre-requisite of 'portable GIT.exe' into the virtual directory of Q:\Aptana.304ģ. gz extension as this is needed for it to become an installer)Ģ. We fire up the Microsoft App-V sequencing / virtualisation wizard and point to the source. Sequencer machine: Windows 7 x86 with App-V 4.6SP1ġ.Browser: Firefox 5.0.1 (virtualised into it's own directory).Target machines: Windows 7 圆4 with App-V SP1.We would choose to not virtualise it but that doesn't seem to be an option. I'm specifically interested in running Aptana on a 64-bit Java version, as the 32-bit version seemingly limits resource usage severely.We have successfully virtualised over 100 applications using Microsoft App-V 4.6 SP1, but are experiencing difficulties sequencing Aptana Studio 3.0.4. (Note: I've seen lots of answers stating that "just using the 32-bit Java" fixes everything. Is the launcher system itself limited to 32-bits and if so, could I "roll my own" to start Aptana in 64-bit mode? There is that -launcher.library bit which reads win32 and x86, which instigates that the launcher cannot handle 64-bits at all. If I attempts to increase the -Xmx and XXMaxPermSize above the value 1386M the IDE fails to start with Cannot start Java virtual machine.
If I attempt to change the -vm argument to a 64-bit Java executable/dll, the IDE fails on startup (either with Cannot start Java virtual machine or dumps the config with exit 13). Is there any way to allow more than the 32-bit limited max heap size for Aptana Studio? Eclipse seemingly allows this, but for some reason Aptana doesn't (Aptana is derived from Eclipse).Ĭurrently my (working) AptanaStudio3.ini looks like the following: -startup
Aptana for windows 7 64 bit Pc#
My PC has a quad-core processor and 16GB of RAM, but Aptana is still so damn slow. I read that the 64-bit compatibility means that a 64-bit OS is supported, but the IDE itself is restricted to a 32-bit Java environment (essentially limiting the maximum allowed memory to be used). When attempting to use a 64-bit Java version, the IDE doesn't load. I'm running Aptana Studio 3.6.1 on 64-bit Windows 7.Īptana site states that the IDE is compatible with 64-bit environments.
0 kommentar(er)
