Sponsored Content
Full Discussion: Eclipse for Solaris 11
Operating Systems Solaris Eclipse for Solaris 11 Post 302779295 by DGPickett on Tuesday 12th of March 2013 12:45:45 PM
Old 03-12-2013
Add /usr/lib/firefox to your $LD_LIBRARY_PATH ?

Since there is no Solaris 11 eclipse, I assume you started with Solaris 10 x86 4.2.1? You might be better off building from source, if this keeps complaining.
 

10 More Discussions You Might Find Interesting

1. Solaris

Eclipse launch question

I just bought my first Ultra 20 (Solaris 10) and I would like to know the step by step directions to launch eclipse please. I have unzipped the eclipse folder in my temp directory I am having really hard time launching eclipse from my desktop. (7 Replies)
Discussion started by: saif
7 Replies

2. Programming

related to Eclipse

I wanted to install similar automake & friends that exist in kdevelop in Eclipse also. There is a project related to this here and the plugins are at Download section. If everyone did it or might do it in the future, I am interested to know how ! If there is somebody else that has another option... (0 Replies)
Discussion started by: mihk
0 Replies

3. UNIX for Dummies Questions & Answers

How to launch Eclipse in Solaris 10

Hi people, i just installed Eclipse on my Solaris terminal and i can't seem to run it. Currently i am using the SSH Client software to go to my Unix console.I tried to run the command "eclipse -vm <path of java hre>" as directed however i still can't run the application. My Command prompt is... (5 Replies)
Discussion started by: wilsontan
5 Replies

4. Programming

eclipse console

I have a C program which ends when user types ctrl-c. this program works fine from terminal but when i launch it from eclipse i can't terminate it correctly with ctrl-c because the console does not read the ctrl-c input command. Can anyone help me?? Thanks (3 Replies)
Discussion started by: littleboyblu
3 Replies

5. Programming

debug with eclipse

Hi, i' m using eclipse 3.2.2 on ubuntu. When i debug a program (C language) i cannot see any variable in the variables view. From the console (debug perspective) i can see the message: no source file named class.c. What is the problem??? thanks (1 Reply)
Discussion started by: littleboyblu
1 Replies

6. Solaris

looking for eclipse for SOLARIS 10 x86-64 bit

Hi, I am looking for eclipse for my solaris 10 x86 64 bit. No luck and haven't found the download yet. It is required when I install WLS 10.3. Of course one no need to use eclipse and you can always use workshop. Does anybody please know where can I download the software. Thanks, ... (2 Replies)
Discussion started by: aa_monster
2 Replies

7. Solaris

install eclipse under solaris without root password?

hi, Ho can I install eclipse under solaris without root password? Thanks. peter (1 Reply)
Discussion started by: laopi
1 Replies

8. HP-UX

Eclipse 3.1 on HP-UX 11i

Hey guys how do you run eclipse on HP-UX 11i? there's a startup.jar and an eclipse file ( which is not an executable ) I get different errors try to run the jar file with different java versions. I have all the possible java vm's installed. (0 Replies)
Discussion started by: binary0x01
0 Replies

9. Solaris

Eclipse for Solaris

i am trying to install weblogic 10.3 but for some component need eclipse from where i can download eclipse and how to install it (2 Replies)
Discussion started by: xxmasrawy
2 Replies

10. Programming

Integrating Jconsole with Eclipse

Hi Guys, I was hoping someone has integrated Eclipse with jconsole to monitor their applications. I have not seen this in action . Any help is much appreciated http://images.devshed.com/fds/smilies/smile.gif Thanks (0 Replies)
Discussion started by: aish11
0 Replies
JH_COMPILEFEATURES(1)						    Javahelper						     JH_COMPILEFEATURES(1)

NAME
jh_compilefeatures - Compiles eclipse features using pde-build. SYNOPSIS
jh_compilefeatures [debhelperoptions] [options] [--pde-build-dir=dir] [feature[...]] DESCRIPTION
jh_compilefeatures is a javahelper program that handles compiling features using pde-build. These features can be specified either in debian/eclipse.features or via command-line. jh_compilefeatures uses debhelper behind the scenes and are therefore subject to the compat level (e.g. when parsing the eclipse.features file). When specifying the dependencies for a feature, jh_compilefeatures will see if this feature has just been compiled and will use the dependency if it is among the results. This can be used together with debian/eclipse.features. Dependencies are always resolved by first checking if it is a recently built feature and if not, then the system installed eclipse's dropins folders will be checked. Currently jh_compilefeatures do not clean up between builds, which means the dependencies for previous builds are present for the current build. Nevertheless, do not rely on this, as this behavior is subject to change. Note: jh_compilefeatures will not rearrange the build order for you in order to do this. Note: that jh_compilefeatures will not error out if it cannot find a missing dependency. This is due to the underlying builder being unable to detect this. FILES
debian/eclipse.features List the eclipse features to compile and their dependencies. The first item on the line is the feature to compile and the following items are considered dependencies. A dependency can either be a dropins folder or a previous built feature. jh_compilefeatures will find it as long as it is installed in the system eclipse's dropins folder or it has just been compiled. OPTIONS
--pde-build-dir=dir Specifies the directory from where pde-build is to be run. Defauls to "debian/.eclipse_build". --feature-deps=deps A space separated list of dependencies. These dependencies will be used to compile all features passed by command-line. Features read from debian/eclipse.features are unaffected by this. --build-opts=args Pass args to the underlying builder. These options are passed to all features built. This defaults to "-DjavacTarget=1.5 -DjavacSource=1.5" if not set. This can be disabled by passing the empty string. --jvm-args=args Pass args to the JVM. These options are passed to all features built. --orbit-dir=dir Specifies where the Orbit dependencies can be found. This is only needed if the orbit dir is in an unusual location. --pde-build=cmd Use a non-standard pde-build command to compile the features. --pde-args=args Passes args directly to pde-build. Note, jh_compilefeatures have specialised options for some of pde-build options and these should be used whenever possible. These options are passed to all features built. --ignore-java-home Skip the check of JAVA_HOME. Since the underlying builder uses ant (and therefore java), the build should ensure it always uses the expected java implementation. Use this if you (for whatever reason) need to declare the specific java implementation without being able to use JAVA_HOME. Note: You still have to tell the underlying builder which java to use. EXAMPLE
A sample debian/eclipse.features org.eclipse.tm.terminal emf org.eclipse.rse.sdk org.eclipse.tm.terminal depends on "emf", which is expected to be found in eclipse's dropins folder. org.eclipse.rse.sdk on the other hand has no dependencies beyond the eclipse platform. If needed you can also specify a previously built feature as a dependency: org.eclipse.some.feature org.eclipse.another.feature org.eclipse.some.feature rse Here org.eclipse.another.feature depends org.eclipse.some.feature, which was just built and also rse, which is expected to be in system installed eclipse's dropins. SEE ALSO
debhelper(7) This program is a part of javahelper and uses debhelper as backend. There are also tutorials in /usr/share/doc/javahelper. AUTHOR
Niels Thykier <niels@thykier.net> COPYRIGHT AND LICENSE
Copyright 2010 by Niels Thykier This tool is free software; you may redistribute it and/or modify it under the terms of GNU GPL 2. 0.43 2011-03-24 JH_COMPILEFEATURES(1)
All times are GMT -4. The time now is 09:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy