|
|
| Re: vmargs are not picked up | 3.6-Targetplatform Product exported in 4.5 IDE (Mars) [message #1703492 is a reply to message #1703452] |
Sat, 01 August 2015 08:50   |
 Daniel Mising name
Messages: 47
Registered: July 2014 |
Member |
|
|
Thank you for your quick answer, Brian!
Quote:[...]when you export it from Eclipse Mars than Eclipse Juno.[...]
I don't think it makes a difference, but im coming from Luna(4.4.x) not Juno(4.2.x).
Quote:[...]My recommendation: adopt Tycho.[...]
I understand that this is a very valid recommendation. I have already tinkered with tycho, liked it but realized that i have made some very wrong decisions when setting up my product ... and sadly these are currently in my way of adopting Tycho.
May i humbly ask again my two questions (or rather i'll stick to one of them)
Quote:- Where can i find info what has changed in the launcher process between luna and mars?
I guess there will be a git repo and the corresponding bugzilla? The URL's to that would help ... I then could poke into that to maybe find some clues as I did not intend to ask for any solution to asking for pointers so that i can search and assess myself.
Actually this different behaviour of the launcher process (concerning picking up the -vmargs) has me puzzled, and currently i am no longer in the "diagnosing mode" ... because i still can supply the -vmargs on the commandline.
I realized that i know nearly nothing (but am curious) about the workings of the launcher ... even more curious after having found (and waded through) the bug concerning the different sized assignable memory sizes (xms/xmx + perm) which apparently is fixed but was(?) caused by the loading of the splashscreen (which split the available Memory when loaded into it) Link to Bug: (onwards from show_bug.cgi?id=188968#c23) So this is rather out of curiosity and learning interests. (2nd edit: The beforementioned Bug was filed under "Product: Equinox / Component: Launcher" ... would this thread more belong to the equinox subforum? I did hope to choose the right forum compartment, but if you seem it more fitting there feel free to move it)
Sorry for this wall of text ... apparently i am not able to contain myself in two lines of text. So Thank you even more when having read this far! :]
Daniel
[Updated on: Sat, 01 August 2015 09:47] Report message to a moderator |
|
|
|
| Re: vmargs are not picked up | 3.6-Targetplatform Product exported in 4.5 IDE (Mars) [message #1704925 is a reply to message #1703584] |
Mon, 10 August 2015 19:04 |
Eclipse User |
|
|
|
Hi Daniel.
Sorry, I should have been a bit more clear in that "product export" is based on PDE Build, which is baroque and hard to diagnose.
The bug you referenced was fixed before the public release of Mars/4.5, so unless you're running on a milestone release (not recommended now that 4.5 is released) then you shouldn't be encountering it. Besides, you're building against a 3.6 target so this code won't be incorporated.
But now that I reread what you wrote:
Quote:
- vm-args are configured in *.product - Launch Arguments
- launching via run/debug recognizes -vmargs
- exported products *.ini file has -vmargs in it
- launching exported product via [product].exe ignores -vmars in [product].ini
It has long been the case that specifying "-vmargs" causes the launcher to ignore all "-vmargs" specified in the .ini file. So what you're seeing is documented behaviour.
There is a new command-line argument "- -launcher.appendVmargs" (specified in the .ini file) that causes any -vmargs on the command-line to be appended to those specified in the .ini file. But that won't work in 3.6.
Brian.
|
|
|
Powered by
FUDForum. Page generated in 0.03606 seconds
] 
Search
Help
Register
Login
Home
