|
|
On Fri, 30 Sept 2022 at 16:43, Albrecht Schlosser wrote:
>
> I'm always using the default build w/o `-A ...` because I can never remember the allowed attribute values (same as for `-T ...`, BTW). But this has nothing to do with the build failure.
>
FWIW, in the "standard"development shell, then "-A x64" seems to give
me a 64-bit sln.
In the "x86 Native" shell, then "-A Win32" seems to yield a 32-bit sln.
> Maybe the MSYS build finds doxygen?
AFAICT, both shells have DOXYGEN in the path.
>
> That said, just for my information: can you please tell me if doxygen was found in *both* builds? You can post the output of the following command in the respective build directories (the output below is from my Linux system):
For a (32-bit) mingw run, I get:
$ grep DOXYGEN CMakeCache.txt
DOXYGEN_DOT_EXECUTABLE:FILEPATH=DOXYGEN_DOT_EXECUTABLE-NOTFOUND
DOXYGEN_EXECUTABLE:FILEPATH=D:/Programs/doxygen/bin/doxygen.exe
//ADVANCED property for variable: DOXYGEN_DOT_EXECUTABLE
DOXYGEN_DOT_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DOXYGEN_EXECUTABLE
DOXYGEN_EXECUTABLE-ADVANCED:INTERNAL=1
For a (32-bit) VS2019 run I get:
DOXYGEN_DOT_EXECUTABLE:FILEPATH=DOXYGEN_DOT_EXECUTABLE-NOTFOUND
DOXYGEN_EXECUTABLE:FILEPATH=D:/Programs/doxygen/bin/doxygen.exe
//ADVANCED property for variable: DOXYGEN_DOT_EXECUTABLE
DOXYGEN_DOT_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DOXYGEN_EXECUTABLE
DOXYGEN_EXECUTABLE-ADVANCED:INTERNAL=1
Basically the same for both (equivalent 64-bit runs also match this...)
This result seems about right, since I do not have dot installed, only doxygen.
HOWEVER:
The MSVC (VS2019) developer shell does not have a valid path that
finds doxygen though, e.g.:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>doxygen
'doxygen' is not recognized as an internal or external command,
operable program or batch file.
Whereas the Msys shell does.
So cmake must be "finding" my doxygen "somehow" in the msvc runs,
using cmake magic (I sometimes wish it would not do that...).
If I invoke doxygen with the path cmake finds, within the msvc dev
shell, it does work (forward slashes notwithstanding):
C:\Program Files (x86)\Microsoft Visual
Studio\2019\Community>D:/Programs/doxygen/bin/doxygen.exe -v
1.9.4 (5d15657a55555e6181a7830a5c723af75e7577e2)
So the build should be able to invoke doxygen OK I think.
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/CAGFM6dZv1mE8FY3BicVC1jCPh3oO3rsCvmsJNP%3Du76UnLRaEYA%40mail.gmail.com.
[ Direct Link to Message ] | |
|
| |