building all (lnm, atools) in Qt: "No rule to make target" atools from lnm #692

u-an-i · 2021-06-13T07:16:05Z

u-an-i
Jun 13, 2021

Qt 5.12.11, Windows, MinGW, release:

:-1: Fehler: No rule to make target 'F:/OneDrive/Dokumente/GitHub/littlenavmap/../build-atools-release/libatools.a', needed by 'littlenavmap.exe'. Stop.

created folder was build-atools-Desktop_Qt_5_12_11_MinGW_64_bit-Release

files inside that are flat, atools .pro implies a /lib subfolder at least.

lnm .pro implies a build-atools-CONF_TYPE thus i wonder why the ...-atools-Desktop-... folder was created.

Answered by u-an-i

Jun 13, 2021

no success.

is not reflected in Qt Creator gui.

build targets in .pro (deploy, copyfiles, all) are not reflected in Qt Creator gui.

Windows has no "copydata" target ! deploy depends on all, all depends on copydata but copydata exists only for linux and mac.

I wonder how "building" from menu did anything at all, assuming qt takes "all" for building because i don't see any mapping done in .pro, and "all" has no commands of its own but only depends on copyall and that does not exits for win, "buildung" in Qt should do nothing -- but it does. "Deployment", which again as assuming automatically takes a target "deploy" because there is no mapping to qt menu commands in .pro, should (try) copy …

View full answer

u-an-i · 2021-06-13T07:33:34Z

u-an-i
Jun 13, 2021
Author

btw.i provided the atools path in the variable, so -CONF_TYPE should not get triggered.

Now checking

0 replies

u-an-i · 2021-06-13T07:39:49Z

u-an-i
Jun 13, 2021
Author

apparent solution:

ATOOLS_LIB_PATH="F:\\OneDrive\\Dokumente\\GitHub\\build-atools-Desktop_Qt_5_12_11_MinGW_64_bit-Release\\"

instead of

ATOOLS_LIB_PATH=F:\OneDrive\Dokumente\GitHub\build-atools-Desktop_Qt_5_12_11_MinGW_64_bit-Release\

also for all other paths.

now build progessing.

But this results in a qmake error about git not being able to "parse-rev" or similar. But build still started. I wonder why git is attempted, i have not configured it inside qt and i see no .pro entry about git.

0 replies

u-an-i · 2021-06-13T07:47:04Z

u-an-i
Jun 13, 2021
Author

according to internet, other possible issue for the error:

space(s) in path(s) -> move
qt got updated and messed up paths -> reinstall qt
order of project references in .pro -> make sure dependent one are before
shadow buil is on -> off

0 replies

u-an-i · 2021-06-13T07:51:26Z

u-an-i
Jun 13, 2021
Author

build progressed, deploy progressed, no errors, no output. No deploy folder. just the build folder with all files flat and an .exe.

0 replies

u-an-i · 2021-06-13T08:12:15Z

u-an-i
Jun 13, 2021
Author

i miss "Create and run the target deploy" from BUILD.txt

Qt "Deploy project" it is not -- does nothing expect some messages "done in 4s"
Qt "create all configurations" it is not -- creates debug et al

Qt options available in menu in menu order:

build project
create all configurations
"build for run" configuration
run qmake
create compilation database
deploy

I try "build for run"

0 replies

u-an-i · 2021-06-13T08:33:38Z

u-an-i
Jun 13, 2021
Author

no success.

is not reflected in Qt Creator gui.

build targets in .pro (deploy, copyfiles, all) are not reflected in Qt Creator gui.

Windows has no "copydata" target ! deploy depends on all, all depends on copydata but copydata exists only for linux and mac.

I wonder how "building" from menu did anything at all, assuming qt takes "all" for building because i don't see any mapping done in .pro, and "all" has no commands of its own but only depends on copyall and that does not exits for win, "buildung" in Qt should do nothing -- but it does. "Deployment", which again as assuming automatically takes a target "deploy" because there is no mapping to qt menu commands in .pro, should (try) copy files -- but does nothing.

peculiar.

10 replies

u-an-i Jun 14, 2021
Author

run far, do you not mind another issue:

F:\OneDrive\Dokumente\GitHub\littlenavmap\etc\SimConnect.dll
1 Datei(en) kopiert
Datei libcrypto-1_1.dll nicht gefunden
0 Datei(en) kopiert
mingw32-make: *** [Makefile:1236: deploy] Error 4
PS F:\OneDrive\Dokumente\GitHub\build-littlenavmap-Desktop_Qt_5_12_11_MinGW_64_bit-Release>

on my whole pc, libcrypto-1_1.dll is only inside OneDrive's app folder and i have the openssl repo built and installed.

u-an-i Jun 14, 2021
Author

i have libcrypto-1_1-x64.dll in lnm folder i copied from openssl i just found :| .

u-an-i Jun 14, 2021
Author

i now let build the 32 bit open ssl dll.

hint for anyone having built 64 bit before and following the instructions from open ssl rep and getting linker conflict error: use nmake clean before configuring 32 bite

u-an-i Jun 14, 2021
Author

deploy succesfull, now looking into the zoom issue. Thank you!

KOKAProduktion Jun 14, 2021

Sry, i forgot about the OpenSSL step... I've added it to the original comment #688 (reply in thread)

u-an-i · 2021-06-14T13:59:45Z

u-an-i
Jun 14, 2021
Author

anyone see also #688 (reply in thread)

12 replies

albar965 Jun 15, 2021
Maintainer

Hope you downloaded the OpenSSL here and did not try to compile it yourself.

About MSVC: Just a question from the slow one (me): You compile with MinGW using the MSVC GUI or not?
qmake can generate MSVC project/solution files as far as I know.

u-an-i Jun 15, 2021
Author

that link leads to no binaries (anymore). i did clone the openssl repo. and succesfully compiled 32 bit and 64 bit now. i set the path in .pro. upon start of lnm i receive warnings about ssl and tls not working but the webserver "works", which is the important thing for me with the built lnm :)

albar965 Jun 15, 2021
Maintainer

🙁 Have to look for another source now or compile on our own. Fortunately this affects only Windows.

KOKAProduktion Jun 15, 2021

Maybe here: https://slproweb.com/products/Win32OpenSSL.html

KOKAProduktion Jun 15, 2021

About MSVC: Just a question from the slow one (me): You compile with MinGW using the MSVC GUI or not?
qmake can generate MSVC project/solution files as far as I know.

Nope, MSVC is just installed on the host and its cmake command is available through PATH.

Which means I only have compiled Marble with it. (cli cmake not MSVC GUI)

The rest is all qmake & MinGW

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

building all (lnm, atools) in Qt: "No rule to make target" atools from lnm #692

{{title}}

Replies: 7 comments 22 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

building all (lnm, atools) in Qt: "No rule to make target" atools from lnm #692

u-an-i Jun 13, 2021

Replies: 7 comments · 22 replies

u-an-i Jun 13, 2021 Author

u-an-i Jun 13, 2021 Author

u-an-i Jun 13, 2021 Author

u-an-i Jun 13, 2021 Author

u-an-i Jun 13, 2021 Author

u-an-i Jun 13, 2021 Author

u-an-i Jun 14, 2021 Author

u-an-i Jun 14, 2021 Author

u-an-i Jun 14, 2021 Author

u-an-i Jun 14, 2021 Author

KOKAProduktion Jun 14, 2021

u-an-i Jun 14, 2021 Author

albar965 Jun 15, 2021 Maintainer

u-an-i Jun 15, 2021 Author

albar965 Jun 15, 2021 Maintainer

KOKAProduktion Jun 15, 2021

KOKAProduktion Jun 15, 2021

u-an-i
Jun 13, 2021

Replies: 7 comments 22 replies

u-an-i
Jun 13, 2021
Author

u-an-i
Jun 13, 2021
Author

u-an-i
Jun 13, 2021
Author

u-an-i
Jun 13, 2021
Author

u-an-i
Jun 13, 2021
Author

u-an-i
Jun 13, 2021
Author

u-an-i Jun 14, 2021
Author

u-an-i Jun 14, 2021
Author

u-an-i Jun 14, 2021
Author

u-an-i Jun 14, 2021
Author

u-an-i
Jun 14, 2021
Author

albar965 Jun 15, 2021
Maintainer

u-an-i Jun 15, 2021
Author

albar965 Jun 15, 2021
Maintainer