[solved] Trying to link my own static libarry
-
If you have a cmake project working why not continue to use cmake ?
-
Because there's no need for that, just do "Open File or Project" and open your top-level CMakeFile.txt
-
Sorry, I meant CMakeLists.txt
-
Aye. Thanks.
I managed to compile pcrio and zlib using CMakeLists.txt with Qt.
Why Qt only shows the CMakeLists.txt and no other files whatsoever?It appears I managed to build both my libraries.
I had to manually tell both library files to CMake Wizard -.--DBoost_IOSTREAMS_LIBRARY_DEBUG:FILEPATH=C:/Boost/lib/libboost_iostreams-mgw49-mt-sd-1_58.a
-DBoost_IOSTREAMS_LIBRARY_RELEASE:FILEPATH=C:/Boost/lib/libboost_iostreams-mgw49-mt-s-1_58.aHow can it be so stupid that it can't see the files unless I toss them on its face?
-
How do you list the files your CMakeLists.txt ?
-
https://github.com/Tapsa/pcrio/blob/master/CMakeLists.txt
https://github.com/Tapsa/genieutils/blob/master/CMakeLists.txtFor genieutils I passed some arguments to CMake:
-DBoost_IOSTREAMS_LIBRARY_DEBUG:FILEPATH=C:/Boost/lib/libboost_iostreams-mgw49-mt-sd-1_58.a
-DBoost_IOSTREAMS_LIBRARY_RELEASE:FILEPATH=C:/Boost/lib/libboost_iostreams-mgw49-mt-s-1_58.a
-DZLIB_LIBRARY:FILEPATH="C:\Cpp\zlib\libz.a"
-DZLIB_INCLUDE_DIR:PATH="C:\Cpp\zlib"
-DEXTERN_DIR:PATH="C:\Users\Tapsa"Is there a better way?
-
You could try to use CMake's finder script for boost and zlib
-
Yeah, but those fail.
find_package(Boost 1.58 COMPONENTS iostreams REQUIRED)
Even if I give as additional argument the boost library folder, it still fails to find it.
It hasn't complained about zlib yet for some reason.Since Qt doesn't save additional arguments anywhere, do I need to put them into the CMakeLists.txt? I used batch scripts to compile my builds before.
Other people who compile my code probably have different paths. What is the best way to extract custom paths so that working with github is easy?I have much more questions about Qt designer etc. You seem to be Qt professional. Do you suggest adding new topics as I proceed coding and googling or can you answer some Qt GUI questions?
-
You would have to give cmake additional paths to search for boost, but it's not something that you can really make generic since on Windows, there's no common place like on *nix systems. Using -DCMAKE_PREFIX_PATH can help.
I can answer them however for other questions not directly related to this thread, you should rather open new topics. That will keep the forum easy to use and search for other users.
-
LOL are you kidding me :D I had these lines AFTER find boost:
set(Boost_USE_STATIC_LIBS ON)
set(Boost_USE_MULTITHREADED ON)
set(Boost_USE_STATIC_RUNTIME ON)Normally I don't even use this make file, but instead I use another for the actual program that uses these libraries. I moved those options above find boost and it works like a charm.
Quick question: what is the fastest list box for over 10 000 items? It needs to have multiple selections and just be basic looking list box. Either it is not list view, or it needs to be adjusted a lot to achieve basic list box look.
-
What do you mean by "list box" ?
-
Like the one in left in this picture:
http://files.heavengames.com/aok/blacksmith/blobs/011002_.jpg
You can see it has bunch of string items (with void pointers to data) and you can select many at once.It's from this program:
http://aok.heavengames.com/blacksmith/showfile.php?fileid=11002 -
If you are talking about the widget on the left, it looks like a QListView with extended selection enabled. What makes you think it needs to be adjusted a lot ?
-
Nice, now I can rebuild my GUI with Qt.
Each item in that list view has its own rounded selection area with dotted outline.
It doesn't look/feel same to wxWidgets list box at all. Default QListView allows items to be moved around and edited their labels too. I disabled moving and label-editing. But if you say that QlistView can be made to look and feel like wxWidgets list box, then I will figure it out myself.You can mark this as solved. I don't know how to mark it.
-
If you need some special visualization then you can subclass QStyledItemDelegate. Apart from that, you have to ponder whether you want to keep the current look and feel of your application or have it more close to what the platform you are targeting offers.
To mark the thread as solved, you can simply edit the title and prepend [solved] :)
Also, consider up-voting the answer(s) that helped you, so other forum users may find them more easily