I am using Eclipse Photon CDT on Windows 10, with all Docker integration Prerequisite already installed.
I have one ubuntu docker image which is running on same machine.
I can check running ubuntu container from Docker Explorer view of Eclipse.
Now I am facing problem in building and launching Hello World C++ simple application inside docker.
When I change my build settings and uncheck build inside container, then application gets built for local environment but when I select run inside container, No binary is formed..
Please help me figuring this out, I am following all steps as defined in latest eclipsecon. Not sure what's wrong.
Please if any one knows about this problem, try to resolve it.
Thanks
The current (and older) release of Eclipse CDT (2018-09) does not print an error if the command in the docker container fails with command not found, see bug 529656. A fix will be included in the December release (2018-12).
The official ubuntu docker image does not include make and g++. Therefore, the build will silently fail. Instead of the ubuntu image, you could use the gcc image.
Related
Until yesterday I had the following dev environment perfectly working:
Ubuntu LTS 20.04
Eclipse (in Snap)
JavaFX (JARs and *.so's in local Folder, --module-path configured in project)
Yesterday "snap" came up and said: stop the app to let updates be installed ... I think, it was talking about Eclipse.
After having Eclipse restarted, my JFx application complained about "glass not being in Java Lib Path". I know this error from Ubuntu LTS 22.04 and could not fix it a month ago (when repairing all paths, you'll end up by some lib ONLY accepting a glibc 2.33, but I already have 2.35) ... that's why I rolled back to 20.04 a month ago :-/
Now this bug hits me again in 20.04 via snap updates.
I drilled the behavior down to having a project's debug commandline, that shows above error. It starts to work as soon as I change that cmd line to NOT use Eclipse's build-in JRE located in Eclipse's snap path. Result: it only works outside of Eclipse now.
Question: does anybody know, how to find the connection in Eclipse's config, that causes Eclipse's Java to use the (obviously freshly installed) snap-version of openjfx (19+11) instead of a working and properly configured (old) local JFx version?
That version seems buggy and does NOT work for Ubuntu 22.04 also in an out-of-the-box installation.
^5
Synopsis
//EDIT: in case this matters ... just saw, that in /snap/eclipse there are TWO versions (60 and 61), with current pointing to 61, BUT the debug-commandline path, showed by Eclipse, uses 60 (not "current and not 61). When I manually launch the Eclipse in 61, it appears completely fresh, without default workspace path and without any plugins.
So when using (on commandline) the java from there, it also works, having no JavaFX plugin under Eclipse dir "61".
I don't reaaly get the idea of a "current" that is unconfigured and all paths pointing to old dir 60 ... obviously my lack of knowledge about snap :-/
I found a workaround: I added an external Java Execution Environment (the system owned JRE) and configured the project to use that.
Now it works again from within Eclipse using the old JFX in my home dir - even the debugger is working fine :-)
But this is no clean solution. I want to have in MY influence, what stuff the internal Java Environments of Eclipse are using. I cannot accept, that the internal JREs are magically connected to some magically appearing snap-app (openjfx 19/11) without even a notice to me or better the option to say "no" to either new snaps or snap updates.
well ... talking to myself :-)
LAST update: some background rollback appears to have sent me to the Test-VM with Ubuntu 22.04 instead of my active VM with Ubuntu 20.04.
So my posted workaround can be regarded as working for those that desparately try to get JavaFX working under 22.04 :-)
So the "problem" I thought to see concerning 20.04 does not exist ... sorry.
I install Cygnus from RPM repository like this and now i dont know how continue.
I try continue whit this section and i got the following error:
bash: APACHE_FLUME_HOME/bin/cygnus-flume-ng: No such file or directory
I am really confused about documentation, because i restart 3 times at start when i try to use docker image, the image got so much errors.
You need java, maven and Flume correctly installed before starting.
export APACHE_FLUME_HOME_BIN=/usr/local/flume to your shell
I recommend following the install from source, which guide you through all the steps.
For docker start with the cygnus-common Dockerfile which uses centos6 as base.
EDIT #2
It works, the first time I installed postgres 64bit, while Qt uses MinGW 32 bit.
EDIT
Following the answer linked by zapredelom, I installed postgres 9 and added to PATH the bin and lib directories. To be sure, I also restarted the machine, but nothing changed. QT_DEBUG_PLUGINS=1 gives me no additional debug infos.
I get this error at runtime:
QSqlDatabase: QPSQL driver not loaded
QSqlDatabase: available drivers: QSQLITE QMYSQL QMYSQL3 QODBC QODBC3 QPSQL QPSQL7
As the error itself displays, postgres driver is already present. Indeed there's a qsqlpsql.dll and qsqlpsqld.dll under C:\Qt\5.8\mingw53_32\plugins\sqldrivers.
I have not built it and I have no Postgres installation on this machine (I test on my Linux OS and deploy on Windows 8.1 VM), the driver was already present after installing QT.
What's the problem?
The driver does not work because it does not find the dependency (it should be depends on libpq.dll), and when you run it, the plugin can not find the required dll. If you are using windows, just try to check using dependencywalker of the qsqlpsql.dll.
You can directly put your libpq.dll to your application exe folder.
PHP Startup: unable to load dynamic library
'C:\xampp\php\ext\php_memcached.dll' -%1 is not a valid Win32
application.
This error is keep showing whenever I restart Apache Server(Using xampp).
I have installed memcached and started using command prompt, memcached.exe -d start and its running fine as I checked task manager.
Now, How to fix it? Am I not using right .dll file?
Try phpinfo() and check right on top, where it says Compiler, if you downloaded the correct VC8/9/10 32/64bit version of the .dll, exchange it - if needed - restart apache and you should be fine. Sometimes this can be a bit tedious to find the corresponding .dll's, good luck!
yes. regardless windows 64, 86 version nor non-thread safe version or other. Try all version to figure out if what version is suite for your xampp.
I am not able to boot the custom webtop. When I boot webtop, I just get the standard version with no ability to install programs, run LXTerm, etc...
I am running a rooted stock Bionic 902
I have applied the HDMI webtop hack
I ran webtop2sd
I ran the custom busybox installer
I applied the e mbm.tar.bz2 patch
I reran the webtop2sd installer.
No change in the webtop that booted after any of those steps.
My diagnostics for webtop2sd is:
version: 2.0.1
Mount executable Version webtop2sd/2.0.0
Custom busybox installed: Y
Webtop configurator version: 33
Currently mounted webtops: webtop, mmcblk0p2
Does anybody have a solution for this?
mbm's patch just enables the gnome terminal in Webtop, so that you can then access other things through command line. try Ctrl-alt-t. that should bring up the Terminal built in to Ubuntu. can you link the mbm.tar.bz2? if you have a working one, which you seem to, i cant find one anywhere! thanks!