Home » Archived » Buckminster » troubles with headless importtarget/importtargetdefintiion
| troubles with headless importtarget/importtargetdefintiion [message #385503] |
Mon, 25 May 2009 13:23  |
 Alex Chatziparaskewas
Messages: 52
Registered: July 2009 |
Member |
|
|
Hi
I am trying to use the importtarget/importtargetdefinition commands in a
headless build of our project using Eclipse 3.5M7. However, the commands
do not seem to work. Something very similar used to work using Eclipse
3.4, so my currently best guesses in regards to this are:
1) I am doing something wrong.
2) The importtarget/importtargetdefinition (is there a difference?)
feature is broken in 3.5.
3) Something has sneaked in between us using it on 3.4 and now using it on
3.5
I have tried 3.2 and 3.5 style target definition files, but to no success.
Currently, I run the following build script:
setpreference
org.eclipse.buckminster.pde.targetPlatformPath=${CC_DEVENV_H OME}\\tools\\buckminster\\tp
lstargets
importtarget "file:///${CC_DEVENV_HOME}/master/root/targets/XX
Components.target
lstargets
which yields the following output:
[java] INFO: setpreference
'org.eclipse.buckminster.pde.targetPlatformPath=Q:/MHDevEnv\ tools\buckminster\tp'
[java] org.eclipse.buckminster.pde.targetPlatformPath set to the
value 'Q:/MHDevEnv\tools\buckminster\tp'
[java] INFO: lstargets
[java] Using workspace at file:/Q:/MHDevEnv/tools/buckminster35/wp/
...
[java] * Directory Q:/MHDevEnv\tools\buckminster\tp :
win32,win32,x86/en_GB
[java] Running Platform :
win32,win32,x86/en_GB
[java] INFO: importtarget
'file:///Q:/MHDevEnv/master/root/targets/XX Components.target'
[java] INFO: lstargets
[java] Using workspace at file:/Q:/MHDevEnv/tools/buckminster35/wp/
...
[java] java.lang.NullPointerException
If I open the created workspace with the Eclipse IDE, I can see some
target defintion 12394284... in the preferences, which I assume has been
created by buckminster, but all tabs are completely empty.
Thanks & Regards
Alex
|
|
|
| Re: troubles with headless importtarget/importtargetdefintiion [message #385504 is a reply to message #385503] |
Mon, 25 May 2009 14:43  |
|
Alex Chatziparaskewas wrote:
> Hi
>
> I am trying to use the importtarget/importtargetdefinition commands in a
> headless build of our project using Eclipse 3.5M7. However, the commands
> do not seem to work. Something very similar used to work using Eclipse
> 3.4, so my currently best guesses in regards to this are:
> 1) I am doing something wrong.
> 2) The importtarget/importtargetdefinition (is there a difference?)
> feature is broken in 3.5.
> 3) Something has sneaked in between us using it on 3.4 and now using it
> on 3.5
>
'importtarget' is an alias for 'org.eclipse.buckminster.pde.importtargetdefinition' which is the full name. Buckminster
will allow the form 'importtargetdefinition' also, as long at is is unique. For a full list of commands, please use the
'lscmds' command.
I very much doubt that you used the importtarget command in 3.4 as it first saw the light of day in the Galileo RC1 release.
> I have tried 3.2 and 3.5 style target definition files, but to no success.
>
> Currently, I run the following build script:
>
> setpreference
> org.eclipse.buckminster.pde.targetPlatformPath=${CC_DEVENV_H OME}\\tools\\buckminster\\tp
>
> lstargets
> importtarget "file:///${CC_DEVENV_HOME}/master/root/targets/XX
> Components.target
> lstargets
>
> which yields the following output:
>
> [java] INFO: setpreference
> 'org.eclipse.buckminster.pde.targetPlatformPath=Q:/MHDevEnv\ tools\buckminster\tp'
>
> [java] org.eclipse.buckminster.pde.targetPlatformPath set to the
> value 'Q:/MHDevEnv\tools\buckminster\tp'
> [java] INFO: lstargets
> [java] Using workspace at file:/Q:/MHDevEnv/tools/buckminster35/wp/ ..
> [java] * Directory Q:/MHDevEnv\tools\buckminster\tp :
> win32,win32,x86/en_GB
> [java] Running Platform :
> win32,win32,x86/en_GB
> [java] INFO: importtarget
> 'file:///Q:/MHDevEnv/master/root/targets/XX Components.target'
> [java] INFO: lstargets
> [java] Using workspace at file:/Q:/MHDevEnv/tools/buckminster35/wp/ ..
> [java] java.lang.NullPointerException
>
> If I open the created workspace with the Eclipse IDE, I can see some
> target defintion 12394284... in the preferences, which I assume has been
> created by buckminster, but all tabs are completely empty.
>
NPE's are never OK so something is obviously wrong here. Can you please run again with --logLevel=DEBUG and
--displayStackTrace. If you get a stack-trace, please open a bugzilla and paste it there. You can also try -consoleLog
(note, just one dash to that one) and see if you get more info that way.
What does your target definition look like?
Regards,
Thomas Hallgren
|
|
|
| Re: troubles with headless importtarget/importtargetdefintiion [message #385505 is a reply to message #385504] |
Tue, 26 May 2009 05:35 |
Alex Chatziparaskewas
Messages: 52
Registered: July 2009 |
Member |
|
|
Hi Thomas
It is true, it did not work in 3.4 neither. I found some ant script
artefacts where I created a 'one directory' target platform from our many
directories, which allows using the 'setpreference
org.eclipse.buckminster.pde.targetPlatformPath=<dir>' directive. So for
the moment I am reusing this for our immediate survival.
For the rest I will raise an issue in bugzilla.
Regards
Alex
Thomas Hallgren wrote:
> Alex Chatziparaskewas wrote:
>> Hi
>>
>> I am trying to use the importtarget/importtargetdefinition commands in a
>> headless build of our project using Eclipse 3.5M7. However, the commands
>> do not seem to work. Something very similar used to work using Eclipse
>> 3.4, so my currently best guesses in regards to this are:
>> 1) I am doing something wrong.
>> 2) The importtarget/importtargetdefinition (is there a difference?)
>> feature is broken in 3.5.
>> 3) Something has sneaked in between us using it on 3.4 and now using it
>> on 3.5
>>
> 'importtarget' is an alias for
'org.eclipse.buckminster.pde.importtargetdefinition' which is the full name.
Buckminster
> will allow the form 'importtargetdefinition' also, as long at is is unique.
For a full list of commands, please use the
> 'lscmds' command.
> I very much doubt that you used the importtarget command in 3.4 as it first
saw the light of day in the Galileo RC1 release.
>> I have tried 3.2 and 3.5 style target definition files, but to no success.
>>
>> Currently, I run the following build script:
>>
>> setpreference
>>
org.eclipse.buckminster.pde.targetPlatformPath=${CC_DEVENV_H OME}\tools\buckminster\tp
>>
>> lstargets
>> importtarget "file:///${CC_DEVENV_HOME}/master/root/targets/XX
>> Components.target
>> lstargets
>>
>> which yields the following output:
>>
>> [java] INFO: setpreference
>>
'org.eclipse.buckminster.pde.targetPlatformPath=Q:/MHDevEnvt oolsbuckminstertp'
>>
>> [java] org.eclipse.buckminster.pde.targetPlatformPath set to the
>> value 'Q:/MHDevEnvtoolsbuckminstertp'
>> [java] INFO: lstargets
>> [java] Using workspace at file:/Q:/MHDevEnv/tools/buckminster35/wp/ ..
>> [java] * Directory Q:/MHDevEnvtoolsbuckminstertp :
>> win32,win32,x86/en_GB
>> [java] Running Platform :
>> win32,win32,x86/en_GB
>> [java] INFO: importtarget
>> 'file:///Q:/MHDevEnv/master/root/targets/XX Components.target'
>> [java] INFO: lstargets
>> [java] Using workspace at file:/Q:/MHDevEnv/tools/buckminster35/wp/ ..
>> [java] java.lang.NullPointerException
>>
>> If I open the created workspace with the Eclipse IDE, I can see some
>> target defintion 12394284... in the preferences, which I assume has been
>> created by buckminster, but all tabs are completely empty.
>>
> NPE's are never OK so something is obviously wrong here. Can you please run
again with --logLevel=DEBUG and
> --displayStackTrace. If you get a stack-trace, please open a bugzilla and
paste it there. You can also try -consoleLog
> (note, just one dash to that one) and see if you get more info that way.
> What does your target definition look like?
> Regards,
> Thomas Hallgren
|
|
|
Goto Forum:
Current Time: Mon Jan 20 17:07:49 GMT 2025
Powered by FUDForum. Page generated in 0.03933 seconds |
] 
Search
Help
Register
Login
Home
