I'm trying to install ADT plug-in in Eclipse 3.5.2 which I got from PowerPC Ubuntu repositories. ADT 16.0.0 or above requires Eclipse 3.6 or higher so I tried 15.0.1 and 9.0.0.
ADT 15.0.1 installation completed 100%, I clicked "Apply Now" and got a bunch of errors. From Error Log:
Invalid preference page path: com.android.ide.eclipse.preferences.main
Problems occurred when invoking code from plug-in: "org.eclipse.ui.intro".
Undefined context while filtering dialog/window contexts
Unable to access file "plugins/org.eclipse.emf.ecore_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.environment_1.0.301.v200908101600.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.xml.ui_1.1.2.v201001222130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.edit_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.equinox.concurrent_1.0.1.R35x_v20100209.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.project.facet.core_1.4.1.v200911141735.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xml.resolver_1.2.0.v200902170519.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.jem.util_2.0.201.v201001252130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.common_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.sse.ui_1.1.102.v200910200227.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.uriresolver_1.1.301.v200805140415.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.edit_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.emfworkbench.integration_1.1.301.v200908101600.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xerces_2.9.0.v200909240008.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.emf_1.1.301.v200908181930.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/javax.xml_1.3.4.v200902170245.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.change_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.xml.core_1.1.402.v201001222130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.frameworks_1.1.300.v200904160730.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.xmi_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xml.serializer_2.7.1.v200902170519.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.ui_1.1.402.v200901262305.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.validation_1.2.104.v200911120201.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.sse.core_1.1.402.v201001251516.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.core_1.1.201.v200806010600.jar!META-INF/MANIFEST.MF".
Invalid preference page path: DDMS
Invalid preference page path: LogCat
ADT 9.0.0 Installation went the same. From Error Log:
Invalid preference page path: com.android.ide.eclipse.preferences.main
Undefined context while filtering dialog/window contexts
Unable to access file "plugins/org.eclipse.emf.ecore_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.environment_1.0.301.v200908101600.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.xml.ui_1.1.2.v201001222130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.edit_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.equinox.concurrent_1.0.1.R35x_v20100209.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.project.facet.core_1.4.1.v200911141735.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xml.resolver_1.2.0.v200902170519.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.jem.util_2.0.201.v201001252130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.common_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.sse.ui_1.1.102.v200910200227.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.uriresolver_1.1.301.v200805140415.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.edit_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.emfworkbench.integration_1.1.301.v200908101600.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xerces_2.9.0.v200909240008.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.emf_1.1.301.v200908181930.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/javax.xml_1.3.4.v200902170245.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.change_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.gef_3.5.1.v20090910-2020.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.xml.core_1.1.402.v201001222130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.frameworks_1.1.300.v200904160730.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.xmi_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xml.serializer_2.7.1.v200902170519.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.ui_1.1.402.v200901262305.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.validation_1.2.104.v200911120201.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.sse.core_1.1.402.v201001251516.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.core_1.1.201.v200806010600.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.draw2d_3.5.2.v20091126-1908.jar!META-INF/MANIFEST.MF".
Invalid preference page path: DDMS
Invalid preference page path: LogCat
Android tab did not appear in Window > Preferences.
Also, both installations took 2 hours.
So, is it possible to install ADT plug-in to Eclipse on PowerPC Ubuntu? Is there any way to install Eclipse 3.6 or 3.7 on my system? My computer is PowerPC G4, Emac (ATI Graphics), Ubuntu 10.04.
First, never install Eclipse from a Linux package manager or repository; always download from www.eclipse.org
The PowerPC linux builds are only available for the Eclipse SDK, not the packages listed on the main Eclipse Downloads page. Here's the link for the latest release of Eclipse (3.7.2/Indigo): http://download.eclipse.org/eclipse/downloads/drops/R-3.7.2-201202080800/index.php
The other thing to make sure of is that you have the Oracle JDK and have configured Eclipse to use it, as described here. Most Linux distros have gcj on the system path and it doesn't play nice with Eclipse.
From there you should be able to install the ADT according to the instructions.
I will throw in here just in case someone runs across my problem
Mint 32 bit, all updates and upgrades applied
sudo apt-get updates
sudo apt-get upgrades)
Eclipsed Indigo Classic - sudo apt-get eclipse
java - sudo apt-get install sun-java6-jdk
Trying to install the Android Eclipse Plugin r18 continually failed with the org.eclipse.wst.sse.core missing error that seems common and random at the same time. Note, this did not happen using 64 bit mint/eclipse etc. go figure. and never on windows.
Here is what I did after trying a lot of different patterns found here on Stack and experimenting using snaps on a virtual box to find the right recipe for me.
Fresh eclipse classic indigo install 3.7.0 (sudo apt-get eclipse) as mentioned above
Start eclipse from the command (sudo eclipse)
Add the repository http://download.eclipse.org/releases/indigo in the Help/Install New Software section
Install Linux tools from the list of options from step 3
After restart try to install the android tools again from the http://dl-ssl.google.com/android/eclipse/ repository ( Success !!! )
After restart CLOSE eclipse (don't let it install the sdk etc)
Start Eclipse normally and let the tools install the SDK for you, or click on the "Window" menu if it doesnt do this immediately on restart to install the base sdk package
Go to the Android SDK manager under the window menu and download any other api's etc you need
This worked for me, many similar things did not, not sure what the differences where etc. and also note I had ZERO issues using 64 bit mint (which is a bit counter intuitive considering the problems the ADB has with 64 bit)
Not THE answer, but certainly an answer for someone having same issues I was (Hopefully)
Related
Question:
Is there a way to install a downloaded NBM (Netbeans Module) into an already installed Netbeans IDE via CLI?
Current setup
Netbeans 12.3 with Windows 10
Netbeans 12.3 with Linux Mint 20.1
Relevant scenario
If the question comes to your mind 'why aren't you just using the GUI?' or anything like that. Think of the following scenario. When working on an air gapped network with 50 computers you're the one having to install Netbeans plugins on all of that PCs. You're able to put files on those PCs and execute a command via console and you don't want to run around all the buildings and clicking through the process.
Thank you very much in advance.
I think I found a solution. I'll post it here to reflect my research because I've never found a answer on stackoverflow.
When Netbeans is already installed you can use the --help parameter like:
C:\Program Files\NetBeans\netbeans\bin\netbeans64.exe --help
This lists lot of available parameters (which I haven't found a list of on the web) like (shortened):
General options:
--help show this help
--jdkhome <path> path to JDK
--console new open new console for output
Module reload options:
--reload /path/to/module.jar install or reinstall a module JAR file
Additional module options:
--modules
--refresh Refresh all catalogs
--list Prints the list of all modules, their versions and enablement status
--install <arg1>...<argN> Installs provided JAR files as modules
--disable <arg1>...<argN> Disable modules for specified codebase names
--enable <arg1>...<argN> Enable modules for specified codebase names
--update <arg1>...<argN> Updates all or specified modules
--update-all Updates all modules
Core options:
--fontsize <size> set the base font size of the user interface, in points
--userdir <path> use specified directory to store user settings
--nosplash do not show the splash screen
In my case the solution was to use the --install parameter pointing to the jar file to install.Be aware that the NBM files are just containers containing the jar file and some more meta data files like config xml files. You're able to open it via 7zip for example. And you'll have to take care of all the dependencies yourself.
I'm trying to debug an open source package, called libprotoident in Eclipse, Kepler version, within Debian. As it has the Makefile, I choose to make an empty Makefile project, and then add all the sources into the workspace. So after that the source compiled and run successfully as in the command line using the Makefile.
As it has 4 apps you can use, I choose to run lpi_protoident package in the run configuration window, as the following image shown.
So the Program ran successfully. Now I'm trying to debug it but it generates the following error.
How can I solve this error and debug the Project?
The file you are trying to debug is most likely a shell script created by automake that acts as a wrapper around the real executable, which has been built in a hidden directory.
Instead of telling Eclipse that tools/protoident/lpi_protoident is your application, try using tools/protoident/.libs/lpi_protoident instead.
General Answer about the error you are getting
What not in executable format: File format not reconized error means is that lpi_protoident is not an executable on the platform you are working on.
Are you sure that is an executable you can run (E.g. from the command line)?
There is also the small chance that the GDB you are using is somehow incompatible with the executable, but that is less likely.
Building libprotoident from source
(Assuming you are trying to build https://github.com/wanduow/libprotoident)
You are trying to build an automake project. The normal way to do that is by configuring to create Makefile, you shouldn't be making your own makefile. Please refer to the README in the project, but the key parts you need to do are:
Installation
After having installed the required libraries, running the following series of commands should install libprotoident
./bootstrap.sh (only if you've cloned the source from GitHub)
./configure
make
make install
By default, libprotoident installs to /usr/local - this can be changed
by appending the --prefix= option to ./configure.
The libprotoident tools are built by default - this can be changed by
using the
--with-tools=no option with ./configure.
I'm new to collectd and Riemann. Im essentially trying to direct collectd logs to a riemann server instance. I understand that I need write_riemann plugin installed. I tried compiling the source files for write_riemann available online, but it includes a file called "riemann.pb-c.h", which is no where to be found. Please help!
Download the binary. After running the build script, while running the configure script include "--enable-write_riemann", this should install it. I had a lot of dependencies missing on CentOS, which threw a lot of errors. Once they were installed, write_riemann plugin was compiled and installed. Another issue you might face while installing the dependency is not able to find the right packages for protobuf-c.I was using yum package installer. Go to sudo vi /etc/yum.repos.d/epel.repo and change enabled from 0 to 1. After this, the protobuf-c processor was recognised while running the configure script. This solved my issue. Hope it does yours too!
I'm trying to get Eclipse to work on my CentOS 7 VM via X11 forwarding. The X11 forwarding seems to be working, as I am able to run and see "xclock". However, whenever I run Eclipse, it crashes with a message similar to this:
java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
/home/centos/eclipse/configuration/org.eclipse.osgi/375/0/.cp/libswt-pi-gtk-4527.so: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory
no swt-pi-gtk in java.library.path
/home/centos/.swt/lib/linux/x86_64/libswt-pi-gtk-4527.so: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory
Can't load library: /home/centos/.swt/lib/linux/x86_64/libswt-pi-gtk.so
This issue is all over the web, and a lot of it is solved my soft linking files in /usr/lib/jni/ to ~/.swt/lib/linux/x86/ but, I do not have a a /usr/lib/jni directory. So, I tried to find the libraries that create this folder upon installation and I found these in another Stack Overflow post: libswt-gtk-3-jni, libswt-gtk-3-java
And I can't seem to find anything on CentOS that provides these. I then found this guide on the CentOS client portal for installing Eclipse and it doesn't work for me. It talks about getting access to devtoolset-3 via RedHat Subscription Manager or RHN Classic, both of which are unavailable to me on the machine that I am working with.
At this point I have JDK installed, and Eclipse untarred and attempting to launch and I'm getting this error. Any ideas?
I am getting a bunch of compile errors when I try to install the MySQL DBD::mysql Perl library. I am trying to install this library on OpenSuse linux (SUSE Linux Enterprise server 10 (x86_64) version 10, patch level 4)
The install fails when trying to compile dbdimp.h. There are hundreds of complile errors but I have reason to believe they all stem from the first 3:
dbdimp.h:23:49: error: mysql.h: No such file or directory
dbdimp.h:24:45: error: mysqld_error.h: No such file or directory
dbdimp.h:26:49: error: errmsg.h: No such file or directory
I believe that the reason I am getting the errors above is that I have no MySql Client installed. I do not know how to install mysql client (I believe I am supposed to get some version of libmysqlclient).
I am brand new to opensuse and vaguely familar with installing packages on Linux in general have used yum, yast, apt-get on ubuntu + centOS previously but the only package manager tools that seem to be on OpenSuse 10 are rpm and zypper. I have not managed to install the required mysql client using either of these. If anyone knows how to install MySql Client to resolve my issue I would greatly appreciate any recomendations
Thanks
You need to install MySQL or the MySQL client libraries, either through your system's package manager or by following the installation instructions from the source code.
It sounds like your question is really "How do I install MySQL on OpenSuse", which would be more appropriate for one of the other StackExchange sites.
I was able to resolve this to a point. In my original question, I stated that I had tried using YAST but that it had not worked. In fact, I did not fully explore the YAST install option but when I did, I managed to download install the required librarys by following an article I found (http://adminramble.com/install-mysql-yast/#chitika_close_button)
I was able to open the YAST GUI in the terminal window (not an X-window display) and navigate through the "software management" section wherein I was able to do a search for MySql. Amoung the search results were mysql client libraries, which I then selected and hit "Accept". The installation started and completed successully.
In order to complile the PERL DBD::mysql module, I had to create a new makefile with the ccflags specified so that the header files could be found:
perl Makefile.PL --cflags -I/usr/include/mysql
I say "to a point" at the top of this comment because I then ran into further problems compiling but my original issue posted has been partially resolved and getting this far may help someone else who is experiencing the same problem. Will update if I get a solution to the compile problem.