Bug 102208 - <launcher>.ini being ignored
Summary: <launcher>.ini being ignored
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Linux-GTK
: P3 minor (vote)
Target Milestone: 3.1.1   Edit
Assignee: Konrad Kolosowski CLA Friend
QA Contact:
URL:
Whiteboard:
Keywords:
: 102207 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-06-29 17:01 EDT by Ian Graham CLA Friend
Modified: 2005-08-02 18:32 EDT (History)
1 user (show)

See Also:

Attachments
launcher.ini that doesn't work under Linux (44 bytes, text/plain)
2005-06-29 17:53 EDT, Ian Graham CLA Friend 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Graham CLA Friend 2005-06-29 17:01:04 EDT 
I've just built my RCP product with the new 3.1 release and the launcher under 
Linux is ignoring the .ini file where I'm trying to specify a VM and VM args.  
And yes, the names match, ie. a "launcher" executable with a "launcher.ini" 
file.  I'm instead having to specify my parameters in the command line.

Under Windows the launcher is picking up the "launcher.ini" properly.
Comment 1 Rafael Chaves CLA Friend 2005-06-29 17:06:22 EDT 
Can you provide the launcher.ini that does not seem to be found?
Comment 2 Ian Graham CLA Friend 2005-06-29 17:53:45 EDT 
Created attachment 24158 [details]
launcher.ini that doesn't work under Linux

OK, I found the problem(hinted at by your request).  It's really actually a PDE
problem in that even for Linux the file is being written out with <cr><lf> -
although the launcher could be made more tolerant.  I resaved the file in Unix
format and it now works fine.
Comment 3 John Arthorne CLA Friend 2005-06-30 10:07:49 EDT 
*** Bug 102207 has been marked as a duplicate of this bug. ***
Comment 4 Rafael Chaves CLA Friend 2005-06-30 10:48:13 EDT 
Ian, where did you generate the faulty launcher.ini? On Windows or Linux?
Comment 5 Ian Graham CLA Friend 2005-06-30 13:06:40 EDT 
Sorry about my spastic finger that double-clicked "Commit", creating two 
reports.

The "bad" launcher.ini was generated when I exported the product from Windows.  
I haven't tried doing it from Linux where I'm even having trouble launching my 
RCP application _within_ Eclipse with the new 3.1(I haven't done any development 
under Linux since M5 or so - I'll report that problem once I have some idea how 
to do so helpfully - for some reason it's not finding the linux/gtk SWT fragment 
even though it's there and checked in the launcher).  In the meantime I'm doing 
all my development and my product builds from Windows.
Comment 6 Rafael Chaves CLA Friend 2005-06-30 13:10:14 EDT 
Ok, that explains it then. 

Wassim, are exported products intended to be multi-platform? Or is the user
expected to be on the target platform while exporting a product?

If it is the latter, this can be closed.
Comment 7 Wassim Melhem CLA Friend 2005-06-30 13:21:52 EDT 
On any platform, you should be able to export to multiple platforms (mac, 
linux, win32) and the correct files should be generated by PDE.

In this case, it appears as though the code reading the init file is too 
stringent, so  we should check the ws-os-arch combination, and generate the 
correct line delimiters.
Comment 8 Wassim Melhem CLA Friend 2005-07-20 13:09:36 EDT 
Konrad, please investigate for 3.1.1
Comment 9 Konrad Kolosowski CLA Friend 2005-08-02 18:32:34 EDT 
Fixed, by using \r\n delimiter on Windows and \n on other platforms in 
eclipse.ini