I am trying to use BinDeps to download a package dependency. After reading the documentation I am still a little confused over the difference between Sources and Binaries.
Can someone explain how they are different?
If I just want to download a .so file from a specified URL, and have it placed in usr/lib, which one should I use?
Thank you.
I believe Sources are for downloading the actual source code of a project which would then use a BuildProcess or SimpleBuild to compile. Binaries is for downloading pre-compiled shared libraries.
Related
Basically, I wrote a program using Go and the binding for the Qt gui library (github.com/bluszcz/cutego). I moved over to the cutego fork because the original binding (github.com/therecipe/qt) isn't being maintained anymore.
My app works great but I need it to run on a machine that needs nothing installed. I'm new to Go so please forgive my ignorance. I followed the instructions to build a static executable here: (https://github.com/therecipe/qt/wiki/Deploying-Windows-to-Windows-64-bit-Static)
I get a few deprecated code warnings but the code does compile. The problem is I still end up with a dynamically compiled executable. I ran ldd using MINGW64 and I get:
Qt5Core.dll => not found
Qt5Gui.dll => not found
Qt5Widgets.dll => not found
As mentioned I am pretty new to Go, but I am also new to this kind of language as I have only developed using Python and VBA. I haven't found any clues online, I think because there's something really obvious that I am missing that everyone else knows about already.
What am I missing here? Any help would be most appreciated!
I would like my executable to be statically typed so that it can run without Qt installed.
When you use cgo, your go executable will link to shared libraries at run time depending on what C libraries the cgo code references.
If you wish to use cgo and have a stand alone executable you need to link your binary to static libraries (typically .a files). It is up to the third party module to provide such libraries, though, and qt may not provide them out of the box.
I found the problem. So with github.com/therecipe/qt you have 2 install options. You can either install the normal default way or you can install using the "static" method. You'll have problems if you do both. I ended up removing all files relative to github.com/therecipe/qt. I then installed using the static Windows x64 to Windows x64 method ONLY and followed those instructions for deploying a static executable. Worked like a charm using the instructions for MYSYS2.
I am trying to use the calendar plug in by jfxtras. I originally tried setting the project up as a maven project or gradle project and importing the jfxtras-all, and setting the snapshot to latest. Unfortunately it seems that iCalendarfx and iCalendarAgenda are not included in this. So I tried just downloading the zip on github. But after setting a file up that had them all in the jfxtras package it gave me a Java.lang.runtime exception. I think maybe it would be best to make a jar of these libraries but I don't really know. Any suggestions as to how to include these libraries would be helpful thanks.
I finally got it working. I included every library in maven separately. For some reason labs has to have a snapshot of 8.0-r4 instead of 8.0-r5. And then I downloaded the zip from github and just included the Java files of iCalendaragenda and iCalendar fx.
I'm a beginner on open source world.
I can compile my own C++ code in VS 2015. but, I have little knowledge about compiling open source code. I can't even find a project file of that.
Anyway, I'd like to compile Sigil 0.9.4 version from source. My system is Windows 10 64 bit, and Qt 5.6.0 is installed. I've been looking for any basic guide for that but I haven't found yet.
I have downloaded a source code zip file from the link
https://github.com/Sigil-Ebook/Sigil/releases
And I have no idea what's the difference between Sigil-0.9.4-Code.zip and Source code (zip).
Which one should I download to compile?
Intuitively, I used 'importing project' in Qt but I get message 'no rule to make target all. stop'
Any instructions for that?
Thank you in advance!!!
For compilation you will need to use CMake. I recommend going through their web-site and read about it.
If you look at the source repository of the software you are trying to build (Sigil), you will see the root folder contains CMakeLists.txt. This is the file that will tell cmake program how to build and configure the software.
If you are planning to use Qt as your IDE, I recommend to download and install cmake first. Then make sure, Qt's toolchain is set up properly with the cmake. Then all you have to do is to open that CMakeLists.txt in Qt (see more details in the aforementioned link). Also, you can find plenty other tutorials on how to use cmake to compile your projects.
Hope this will help you get started.
I'm trying to write a simple Qt app that will access zip files and read the content of these zip files (the content are text files). Many posts says that Quazip is the solution.
Being new to Qt and coming from .Net background, I really don't know how to use the Quazip, I downloaded the Quazip source but I'm not sure, should I compile it or should I use the source code in my project. I really have no clue.
Any help is much appreciated.
Regards.
It seems as you have various options. You can use source code immediately by copying the relevant files into your project. By default however a static library is compiled when you run
> make install
and in that case you need to add the relevant path to your .pro file so that it finds is static library.
Well, you have several options:
Just add the sources to your project. Pros: you can modify them if you want without affecting your other projects. Cons: updating QuaZip is probably going to be a maintenance headache.
Compile it as a static library (qmake CONFIG+=staticlib). Pros: updating is easier as you don't have to deal with structural changes, only recompile QuaZip and rebuild/relink your projects. Cons: you still have to recompile and relink.
Compile QuaZip as a shared (DLL) library. Pros: updating is extremely easy provided that the new version maintains binary compatibility, plus the code is shared among various applications running at the same time. Cons: it will break everything (that is, until you rebuild/relink your apps) if the new version doesn't maintain binary compatibility.
If you just need to read some zip files in some random project, any of these three will do fine. You probably won't have to update QuaZip either, unless you find some bugs that need to be fixed.
As for the binary compatibility: it is guaranteed that third level version changes (x.y.z1 -> x.y.z2) are binary compatible. As for minor version changes (x.y1 -> x.y2), they probably won't be binary compatible for some time, until the Pimpl idiom is implemented properly.
I downloaded the qt embedded demo source code recently on my linux machine. Following are the outcomes during running of the program
I compiled it statically on my x86 machine and run the application on x86 machine it runs fine. But when i took the statically compiled binary file to other machine with Atom platform It run with some missing widgets. I found that the plugins cant be ported with static compilation. Can anybody tell me is it true? If no can anybody tell me the steps for it?
I compiled it dynamically with shared libraries. Then got an executalbe on linux. I did "ldd MyAppName". It show me the shared library files it is using. But I dont know how to package these. Can anybody tell me the steps to package it?
I checked in the article on deploying qt applications on X11-linux platforms. But its not complete. Can anybody give me the detailed steps?
Any help will be appreciated......
you either have a distro, that does'nt support atom, or libraries, that are not compiled with support for it. either way - something somewhere on your system (or your qt) is not compiled for atom
The problem is that you are compiling your app, and its libraries (static or dynamic) work for x86, not for Atom. Perhaps you are able to create some sort of fat binary (lipo?) so that pieces of your app will function on x86 and Atom, but bits using the x86-only libraries will not function on Atom. (Right? That's a concise definition of your problem?)
If you have the source code for the libraries that don't run on Atom, and they're important to you, you should consider porting the code to Atom. If it's open-source code, you can contribute to the project. While you didn't give many details, my (very generic) approach to this would be to get the code on an Atom machine, write a very short test application for the library, and work out the issues.
Re #2: There's little difference between compiling an app and linking to shared libraries or dynamic libraries. On your x86 machine, if you have this code (these "plugins") compiled as dynamic libraries, it's pretty much the same as statically linking those binaries into the app. These libraries will work on x86, whether they're dynamically or statically linked.
I'm not sure if that helps very much -- if you're getting binary Qt plugins as static or dynamic libraries without source, you're out of luck. Submit a bug report. If you have source code, you can do a lot more.
I just dynamically compiled my application and ported to atom platform. I found the dependencies and ported them also and set the environment variable LD_LIBRARY_PATH on target machine to my ported shared libraries and It worked. Thanks everybody for your suggestions