The Open JavaFX binary releases have moved to gluon but they don't include any source release on the download page. Even if it was provided (and it isn't) instructions and a link to a version control system is insufficient given OpenJavaFX is GPL 2. e.g. https://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.en.html#DistributeWithSourceOnInternet
Will such a release ever be provided. And the same question goes for javadocs suitable for an ide.
Related
I know there's https://dotnet.microsoft.com/download for most Linux versions, but I wasn't able to get any of them running on my Raspberry. I was lucky to find a blog with the direct link for wget.
I'm not asking for current links, I'm asking for how i can get the current stable version for future releases, or even better where i find links for every version available.
Look at the real download page: https://dotnet.microsoft.com/download/dotnet-core/3.0
You can find links to ".NET Core binaries" under the "Linux" section for each release on that page.
These are not stable links - each time there is a release, you will have to look and and find the link to the latest release (a new row in the table) manually.
You should use the "ARM64" or "ARM32" links depending on what your Raspberry Pi version is.
These binaries are "portable", meaning they should work irrespective of what distro you are using (as long as it's a recent-enough distro).
There is a issue that is present with some very specific aspect of applications I build using a Qt library provided in repositories of the system I'm using; this issue isn't present with the same numerical build of Qt that I built myself on this exact system.
I would like to query all information about build environment of Qt, it's configuration flags, etc., anything that could help me determine the difference between two build of Qt library.
I've learned about config.summary file, that is present in mine qtbase sources, but there isn't a counterpart anywhere in the system for pre-built version (I have, besides headers, installed a sources and debug information for the qt library packages).
I also tried looking for some header files that could specify, for example, what features were enabled at the build time, but could't locate anything like that (mostly because I don't know the name or some example contents of such file so that I could search for it or grep it), so if there is indeed such file, please point me to it.
I think the best reply is to quote this answer from Qt mailing list
Unfortunately it isn't that easy to figure out but the data is
available; you just need to know from where to search it :D
Configure options can be found from (qtbase) build log, from qt5.git
integration. E.g for 5.6.3
here:https://testresults.qt.io/coin/integration/qt/qt5/tasks/1505476672
and for 5.9.5 here:
https://testresults.qt.io/coin/integration/qt/qt5/tasks/1523412986
And SW details here: https://wiki.qt.io/Qt_5.6_Tools_and_Versions &
https://wiki.qt.io/Qt_5.9_Tools_and_Versions
You can find the latest builds at https://testresults.qt.io/coin/?project=qt%2Fqt5
If you look inside the "Build" section you have all the system configurations Qt is built for (column "Target") and for each configuration the parameters (column "Configure Arguments").
I want to use Qt 5.10.1 with Vulkan. I downloaded prebuilt gcc_64 version, opened hellowulkanwindow application, set VULKAN_SDK in build environment. But the compilation gives me a lot of errors, for example 'QVulkanWindow' does not name a type. It looks like the macro QT_CONFIG(vulkan) return false, but I'm pretty sure that prebuilt version should come with Vulkan enabled.
VulkanSDK installed on my system, I can run demos. Also I can run non-qt code which uses Vulkan.
So how to check that feature QT_FEATURE_vulkan is enabled?
Upd: I ran configure -list-features in 5.10.1 sources and it didn't showed me anything related to Vulkan.
You can check the QT_FEATURE_vulkan definition in the qtgui-config.h header file (1 means enabled, -1 means disabled). You can just type QT_FEATURE_vulkan in Qt Creator and press F2 to nagivate to its location in the header file.
Apparently Qt 5.10.0 and 5.10.1 provided by the official installer do not have Vulkan support enabled, at least on Linux.
I'm using Ubuntu 16.10. Installed Kaa Sandbox and tested with notification demo in terminal. I'm using CCSv7 to program on CC3200. I confused what is correct way to create project in CCS with Kaa SDK generate from Kaa Sandbox. Here is how I do but I can't build project:
Generate SDK and run build by cmake with target platform is cc32xx, I use notification example
Create new project then include Kaa SDK path
Include Kaa file library (*.a): libkaac.a, libextension_user.a, libextension_event.a, libextension_logging.a, libextension_profile.a, libextension_bootstrap.a, libextension_notification.a, libextension_configuration.a, libmbedtls.a, librsa_keygen.a. I'm not sure that need all of them but just include all to prevent error.
Copy some code from kaa_demo.c and blinky demo project to my main.c.
Hit build. Error occur that libmbedtls.a not build for ARM so I go to folder thirdparty and build it. Solved.
Occur another error: Description Resource Path Location Type
#10099-D program will not fit into available memory. placement with alignment fails for section ".cinit" size 0xc41 . Available memory ranges: cc3200v1p32.cmd /demo1 line 75 C/C++ Problem. I try to increase or decrease stack size but not work.
More error: Description Resource Path Location Type
unresolved symbol __assert_func, first referenced in /opt/ti/kaa-sdk/build/libkaac.a demo1 C/C++ Problem. This error occur when missing include library file but it occur in another library file so I dont know how to fix.
Anyone can help me or suggest how to make a project for CC3200 with Kaa SDK, in any IDE. Its take me 2 weeks.
At the moment of Kaa 0.10.0 release the CC32xx sample applications were broken due to the same issue you mentioned in 7). The binary build did not fit into the CC32xx program memory. That is why whole the CC32xx platform was disabled in the Kaa 0.10.0 Sandbox release.
Now, the issue on the GitHub repository is fixed and the CC32xx platform will be re-enabled in the Kaa 0.10.1 Sandbox release (comming soon). So, you can either wait for the Kaa 0.10.1 release or try building the CC32xx application with the CMake from GitHub.
Regarding your question for build from CCSv7 IDE directly you should search for integration of CMake builds into the CCSv7 IDE. Kaa team does not provide such integration for now considering you should use any IDE you prefer for development and build by CMake (manually or from IDE).
I'm developing a closed source application and to do so in accordance with the LGPL I have to dynamically link Qt's libraries to my application. Does Qt do this by default or do I have to take steps to do so? If that's the case how would I go about doing it?
Qt uses dynamic linking by default.
You'll notice this immediately during deployment to a non-developer machine, because your code will not run without the Qt libraries.
If your concern is the LGPL, just be careful when compiling Qt itself. Most LGPL violations with Qt are not because of static linking (since dynamic is the default), but for compiling Qt with non-default parameters.
LGPL is not just that the library must be provided along your binaries, but also that you specify how your users can build themselves the LGPL part. If you compile Qt yourself and do not use the pre-compiled binaries from the website, you must document that part of your build configuration in your release!
As soon as you get something running on your program, start preparing a release version for a non-developer environment without Qt installed. Your program should fail as soon as you delete the DLLs that you must copy along your program (or whatever format your OS uses).
It does it by default, statically linking seems to be quite involved judging by the many questions on the site regarding it.