subject:"Re\: Compiling with Microsoft Visual C\+\+"

racoon wrote:

> On 11.07.2016 17:43, racoon wrote:
>>
>> If I provide just those CMake gives me an error:
>>
>> ---
>>
>> Make Error at CMakeLists.txt:601 (find_package):
>>   By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this project
>> has
>>   asked CMake to find a package configuration file provided by
>> "Qt5Core", but
>>   CMake did not find one.
>>
>>   Could not find a package configuration file provided by "Qt5Core" with
>> any
>>   of the following names:
>>
>> Qt5CoreConfig.cmake
>> qt5core-config.cmake
>>
>>   Add the installation prefix of "Qt5Core" to CMAKE_PREFIX_PATH or set
>>   "Qt5Core_DIR" to a directory containing one of the above files.  If
>>   "Qt5Core" provides a separate development package or SDK, be sure it
>>   has been installed.
>>
>> ---
>>
>> Only after adding the CMAKE_PREFIX_PATH
>>
>> C:/Qt/Qt5.6.1/5.6/msvc2015/
>>
>> I get rid of the error. (Maybe I it is because Qt is missing in my PATH
>> variable?)

Did you try whether adding C:/Qt/Qt5.6.1/5.6/msvc2015/bin to PATH fixes the 
problem even if CMAKE_PREFIX_PATH is empty? I ask because the current 
installation instructions ask to add the qt dir to PATH, and if that does 
not work we'll need to change them.

>> It still gives me some other. But maybe I don't need to worry about
>> these?
>>
>> ---
>>
>> Function magic_file not found
>> Function magic_open not found
>> Function magic_load not found
>> Function magic_close not found
>> Function magic_error not found
>> Could NOT find Magic (missing:  Magic_INCLUDE_DIR Magic_LIBRARY
>> HAS_MAGIC_FUNCTIONS)
>>   * Hunspell:
>>  - include: C:/LyX/lyx-23/3rdparty/hunspell/1.3.3/src
>>  - library: hunspell
>> Could NOT find ASPELL (missing:  ASPELL_LIBRARY ASPELL_INCLUDE_DIR)
>> ASPELL not found, building without ASPELL support
>> Could NOT find ENCHANT (missing:  ENCHANT_LIBRARY ENCHANT_INCLUDE_DIR)
>> ENCHANT not found, building without Enchant support
>> Building with USE_HUNSPELL

These are expected. All these libraries are optional, libmagic is for file 
type detection and the other ones for spelling. If libmagic is not found a 
builtin fallback is used, and for spelling you can either use aspell, 
enchant or hunspell, and the latter one is included in 3rdparty.

> Okay, after compiling INSTALL I copied the dependencies and Qt dlls. In
> addition to the ones mentioned in the INSTALL.Win32 I had to copy
> 
> Qt5Widgets(d).dll
> Qt5WinExtras(d).dll

I added these to INSTALL.Win32.

However, it would be better if the automatism provided by cmake to xopy the 
needed dlls into the install location would work. I guess that the reason 
why it did not work is the missing qt directory in PATH. It would be nice if 
you could try that out.

Georg

Re: Compiling with Microsoft Visual C++

racoon wrote:

> On 11.07.2016 16:05, racoon wrote:
>>
>> Did click on "Build" (is that the same as compile?) from the context
>> menu of "LyX" in the Solution Explorer. And it compiled with no errors.

Yes I meant build (this is the MSVc terminology).

>> Pressed F5, got a message about outdated files. Choose "Yes" to build
>> them. Got an error message (attached).
> 
> I guess I have to set LyX as my startup project (in the Solution
> Explorer from the context menu of "LyX" choose "Set as StartUp
> Project"). Before "ALL_BUILD" was the startup project.

Yes, LyX should be the startup project.

> Okay. After pressing F5 I get an error message for a missing Qt library
> (attached) and LyX won't run...

This should be fixable as well by adding C:/Qt/Qt5.6.1/5.6/msvc2015/bin to 
the PATH.


Georg

Re: Compiling with Microsoft Visual C++

Richard Heck wrote:

> If you're running LyX from a terminal, you should get some output
> explaining why reconfiguration is failing.

Unfortunately this is more complicated on windows than on other operating 
systems. An application is either a console application (with 
stdin/stdout/stderr and usually without GUI windows), or a GUI application 
(without stdin/stdout/stderr and usually with GUI windows). If you start a 
console application it will always open a terminal window, and this is the 
reason why one usually does not want this for an application that creates 
GUI windows.

See also the big comment in src/support/os_win32.cpp. By default, LyX is 
compiled as GUI app, meaning any stuff sent to stderr or stdout will vanish 
in a black hole, and nobody will ever see it. LyX can be compiled as a 
console app by calling cmake with CONSOLE=FORCE.

Georg

Re: Compiling with Microsoft Visual C++

racoon wrote:

> On 12.07.2016 16:48, Richard Heck wrote:
>>
>> The python executable is not being found. Is it in your path? I would
>> guess that this is something the installer usually takes care of.
> 
> Thanks. The python path was actually not in my path variable.  Now it
> works. I don't know why these paths are not added by default...

Please don't forget that you are walking on new ground: To my knowledge, 
nobody did run LyX on windows without using the installer up to now. Even 
Uwe (who builds the windows executables since many years) creates all needed 
settings with the installer, and copies newly built executables into the 
installation for testing.

Therefore, the only place where the python executable could be put into the 
PATH would be when you run the python installer. IIRC it has an option to 
update PATH, which you can select or not.

Georg

Re: Compiling with Microsoft Visual C++

racoon wrote:

> Final warnings I get are of the following form:
> 
> 3>  Generating LyX2.3.pot
> 3>CUSTOMBUILD : cygwin warning :
> 3>MS-DOS style path detected: C:/LyX/lyx-23-build/po/POTFILES.in
> 3>Preferred POSIX equivalent is:
> /cygdrive/c/LyX/lyx-23-build/po/POTFILES.in
> 3>CYGWIN environment variable option "nodosfilewarning" turns off
> this warning.
> 3>Consult the user's guide for more details about POSIX paths:
> 3>  http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
> 
> Since these are only warning, I am not sure whether I should bother.

You have a cygwin python in your PATH environment variable. This might work, 
but it would be more safe to put a native windows python into the path in 
front of the cygwin one.


Georg

Re: Compiling with Microsoft Visual C++

2016-07-12 Thread racoon


Final warnings I get are of the following form:

3>  Generating LyX2.3.pot
3>CUSTOMBUILD : cygwin warning :
3>MS-DOS style path detected: C:/LyX/lyx-23-build/po/POTFILES.in
3>Preferred POSIX equivalent is: 
/cygdrive/c/LyX/lyx-23-build/po/POTFILES.in
3>CYGWIN environment variable option "nodosfilewarning" turns off 
this warning.

3>Consult the user's guide for more details about POSIX paths:
3>  http://cygwin.com/cygwin-ug-net/using.html#using-pathnames

Since these are only warning, I am not sure whether I should bother.

Daniel

Re: Compiling with Microsoft Visual C++

2016-07-12 Thread racoon


On 12.07.2016 16:48, Richard Heck wrote:

On 07/12/2016 01:54 AM, Daniel wrote:

On 12.07.2016 00:16, Richard Heck wrote:

OK. Try opening the messages pane: View> Messages Pane. Then
reconfigure.


Okay. Here is the full log:

[snip]

07:53:18.990: Running configure...
07:53:19.039: The process failed to start. Either the invoked program
is missing, or you may have insufficient permissions to invoke the
program.
07:53:19.076: Reloading configuration...LyX: reconfiguring user directory
C:\LyX\lyx-23\src\support\Systemcall.cpp (260): Systemcall: 'python
-tt "C:/LyX/lyx-23/lib/configure.py"
--binary-dir="C:/LyX/lyx-23-build/LYX_INSTALLED/bin/"' did not start!
C:\LyX\lyx-23\src\support\Systemcall.cpp (261): error The process
failed to start. Either the invoked program is missing, or you may
have insufficient permissions to invoke the program.


The python executable is not being found. Is it in your path? I would
guess that this is something the installer usually takes care of.


Thanks. The python path was actually not in my path variable.  Now it 
works. I don't know why these paths are not added by default...


Daniel

Re: Compiling with Microsoft Visual C++

2016-07-12 Thread Richard Heck

On 07/12/2016 01:54 AM, Daniel wrote:
> On 12.07.2016 00:16, Richard Heck wrote:
>> OK. Try opening the messages pane: View> Messages Pane. Then
>> reconfigure.
>
> Okay. Here is the full log:
>
> [snip]
>
> 07:53:18.990: Running configure...
> 07:53:19.039: The process failed to start. Either the invoked program
> is missing, or you may have insufficient permissions to invoke the
> program.
> 07:53:19.076: Reloading configuration...LyX: reconfiguring user directory
> C:\LyX\lyx-23\src\support\Systemcall.cpp (260): Systemcall: 'python
> -tt "C:/LyX/lyx-23/lib/configure.py"
> --binary-dir="C:/LyX/lyx-23-build/LYX_INSTALLED/bin/"' did not start!
> C:\LyX\lyx-23\src\support\Systemcall.cpp (261): error The process
> failed to start. Either the invoked program is missing, or you may
> have insufficient permissions to invoke the program.

The python executable is not being found. Is it in your path? I would
guess that this is something the installer usually takes care of.

Note that not finding python will cause all kinds of other problems, too.

Richard

Re: Compiling with Microsoft Visual C++

2016-07-11 Thread Daniel


On 12.07.2016 00:16, Richard Heck wrote:

OK. Try opening the messages pane: View> Messages Pane. Then reconfigure.


Okay. Here is the full log:

Error: Document class not found

The layout file:
article
could not be found. A default textclass with default
layouts will be used. LyX will not be able to produce
correct output.
Warning: Module not available

The module basic has been requested by
this document but has not been found in the list of
available modules. If you recently installed it, you
probably need to reconfigure LyX.

23:55:40.303: (buffer-new: Ctrl+N)
23:57:47.908: (icon-size 10)
23:58:06.276: (icon-size 100)Warning: Module not available

The module basic has been requested by
this document but has not been found in the list of
available modules. If you recently installed it, you
probably need to reconfigure LyX.

07:31:21.772: Automatic save done.
07:31:31.012: (icon-size 20)
07:31:38.464: (icon-size 100)Warning: Module not available

The module basic has been requested by
this document but has not been found in the list of
available modules. If you recently installed it, you
probably need to reconfigure LyX.

07:50:26.694: Automatic save done.
07:53:14.166: (dialog-toggle progress)
07:53:18.990: Running configure...
07:53:19.039: The process failed to start. Either the invoked program is 
missing, or you may have insufficient permissions to invoke the program.

07:53:19.076: Reloading configuration...LyX: reconfiguring user directory
C:\LyX\lyx-23\src\support\Systemcall.cpp (260): Systemcall: 'python -tt 
"C:/LyX/lyx-23/lib/configure.py" 
--binary-dir="C:/LyX/lyx-23-build/LYX_INSTALLED/bin/"' did not start!
C:\LyX\lyx-23\src\support\Systemcall.cpp (261): error The process failed 
to start. Either the invoked program is missing, or you may have 
insufficient permissions to invoke the program.

LyX: Done!
07:53:22.356: (reconfigure)

Re: Compiling with Microsoft Visual C++

2016-07-11 Thread Richard Heck

On 07/11/2016 05:31 PM, Daniel wrote:
> On 11.07.2016 23:05, Richard Heck wrote:
>> On 07/11/2016 02:49 PM, Daniel wrote:
>>> On 11.07.2016 19:53, Richard Heck wrote:
 On 07/11/2016 12:18 PM, racoon wrote:
>
> Now LyX is actually running!!! But it complains about missing
> "textclasses" and reconfigure does not work properly (screenshots
> attached).

 If you're running LyX from a terminal, you should get some output
 explaining why reconfiguration is failing.
>>>
>>> Unfortunately not. I just ran LyX.exe in the terminal (on Windows
>>> cmd.exe) but it was silent when the "errors" happened. Or is there a
>>> "verbose" option?
>>
>> Was there any output at all when you tried to reconfigure?
>
> None.

OK. Try opening the messages pane: View> Messages Pane. Then reconfigure.

Richard

Re: Compiling with Microsoft Visual C++

2016-07-11 Thread Daniel


On 11.07.2016 23:05, Richard Heck wrote:

On 07/11/2016 02:49 PM, Daniel wrote:

On 11.07.2016 19:53, Richard Heck wrote:

On 07/11/2016 12:18 PM, racoon wrote:


Now LyX is actually running!!! But it complains about missing
"textclasses" and reconfigure does not work properly (screenshots
attached).


If you're running LyX from a terminal, you should get some output
explaining why reconfiguration is failing.


Unfortunately not. I just ran LyX.exe in the terminal (on Windows
cmd.exe) but it was silent when the "errors" happened. Or is there a
"verbose" option?


Was there any output at all when you tried to reconfigure?


None.

Daniel


---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: Compiling with Microsoft Visual C++

2016-07-11 Thread Richard Heck

On 07/11/2016 02:49 PM, Daniel wrote:
> On 11.07.2016 19:53, Richard Heck wrote:
>> On 07/11/2016 12:18 PM, racoon wrote:
>>>
>>> Now LyX is actually running!!! But it complains about missing
>>> "textclasses" and reconfigure does not work properly (screenshots
>>> attached).
>>
>> If you're running LyX from a terminal, you should get some output
>> explaining why reconfiguration is failing.
>
> Unfortunately not. I just ran LyX.exe in the terminal (on Windows
> cmd.exe) but it was silent when the "errors" happened. Or is there a
> "verbose" option?

Was there any output at all when you tried to reconfigure?

Richard

Re: Compiling with Microsoft Visual C++

2016-07-11 Thread Daniel


On 11.07.2016 19:53, Richard Heck wrote:

On 07/11/2016 12:18 PM, racoon wrote:


Now LyX is actually running!!! But it complains about missing
"textclasses" and reconfigure does not work properly (screenshots
attached).


If you're running LyX from a terminal, you should get some output
explaining why reconfiguration is failing.


Unfortunately not. I just ran LyX.exe in the terminal (on Windows
cmd.exe) but it was silent when the "errors" happened. Or is there a
"verbose" option?

Daniel


---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: Compiling with Microsoft Visual C++

2016-07-11 Thread Richard Heck

On 07/11/2016 12:18 PM, racoon wrote:
>
> Now LyX is actually running!!! But it complains about missing
> "textclasses" and reconfigure does not work properly (screenshots
> attached).

If you're running LyX from a terminal, you should get some output
explaining why reconfiguration is failing.

Richard

Re: Compiling with Microsoft Visual C++


On 11.07.2016 17:43, racoon wrote:

On 10.07.2016 20:35, Georg Baum wrote:

Only LYX_USE_QT, LYX_DEPENDENCIES_DOWNLOAD and LYX_INSTALL should be
needed.
CMAKE_PREFIX_PATH does probably have no effect, it should be
C:/Qt/Qt5.6.1/5.6/msvc2015/bin unless C:/Qt/Qt5.6.1/5.6/msvc2015/bin is
already in the system path.


If I provide just those CMake gives me an error:

---

Make Error at CMakeLists.txt:601 (find_package):
  By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this project
has
  asked CMake to find a package configuration file provided by
"Qt5Core", but
  CMake did not find one.

  Could not find a package configuration file provided by "Qt5Core" with
any
  of the following names:

Qt5CoreConfig.cmake
qt5core-config.cmake

  Add the installation prefix of "Qt5Core" to CMAKE_PREFIX_PATH or set
  "Qt5Core_DIR" to a directory containing one of the above files.  If
  "Qt5Core" provides a separate development package or SDK, be sure it has
  been installed.

---

Only after adding the CMAKE_PREFIX_PATH

C:/Qt/Qt5.6.1/5.6/msvc2015/

I get rid of the error. (Maybe I it is because Qt is missing in my PATH
variable?)

It still gives me some other. But maybe I don't need to worry about these?

---

Function magic_file not found
Function magic_open not found
Function magic_load not found
Function magic_close not found
Function magic_error not found
Could NOT find Magic (missing:  Magic_INCLUDE_DIR Magic_LIBRARY
HAS_MAGIC_FUNCTIONS)
  * Hunspell:
 - include: C:/LyX/lyx-23/3rdparty/hunspell/1.3.3/src
 - library: hunspell
Could NOT find ASPELL (missing:  ASPELL_LIBRARY ASPELL_INCLUDE_DIR)
ASPELL not found, building without ASPELL support
Could NOT find ENCHANT (missing:  ENCHANT_LIBRARY ENCHANT_INCLUDE_DIR)
ENCHANT not found, building without Enchant support
Building with USE_HUNSPELL

---


Okay, after compiling INSTALL I copied the dependencies and Qt dlls. In
addition to the ones mentioned in the INSTALL.Win32 I had to copy

Qt5Widgets(d).dll
Qt5WinExtras(d).dll

Now LyX is actually running!!! But it complains about missing
"textclasses" and reconfigure does not work properly (screenshots
attached).

Daniel


---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: Compiling with Microsoft Visual C++


On 10.07.2016 20:35, Georg Baum wrote:

Only LYX_USE_QT, LYX_DEPENDENCIES_DOWNLOAD and LYX_INSTALL should be needed.
CMAKE_PREFIX_PATH does probably have no effect, it should be
C:/Qt/Qt5.6.1/5.6/msvc2015/bin unless C:/Qt/Qt5.6.1/5.6/msvc2015/bin is
already in the system path.


If I provide just those CMake gives me an error:

---

Make Error at CMakeLists.txt:601 (find_package):
  By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this
project has
  asked CMake to find a package configuration file provided by
"Qt5Core", but
  CMake did not find one.

  Could not find a package configuration file provided by "Qt5Core"
with any
  of the following names:

Qt5CoreConfig.cmake
qt5core-config.cmake

  Add the installation prefix of "Qt5Core" to CMAKE_PREFIX_PATH or set
  "Qt5Core_DIR" to a directory containing one of the above files.  If
  "Qt5Core" provides a separate development package or SDK, be sure it has
  been installed.

---

Only after adding the CMAKE_PREFIX_PATH

C:/Qt/Qt5.6.1/5.6/msvc2015/

I get rid of the error. (Maybe I it is because Qt is missing in my PATH
variable?)

It still gives me some other. But maybe I don't need to worry about these?

---

Function magic_file not found
Function magic_open not found
Function magic_load not found
Function magic_close not found
Function magic_error not found
Could NOT find Magic (missing:  Magic_INCLUDE_DIR Magic_LIBRARY
HAS_MAGIC_FUNCTIONS)
  * Hunspell:
 - include: C:/LyX/lyx-23/3rdparty/hunspell/1.3.3/src
 - library: hunspell
Could NOT find ASPELL (missing:  ASPELL_LIBRARY ASPELL_INCLUDE_DIR)
ASPELL not found, building without ASPELL support
Could NOT find ENCHANT (missing:  ENCHANT_LIBRARY ENCHANT_INCLUDE_DIR)
ENCHANT not found, building without Enchant support
Building with USE_HUNSPELL

---

Daniel


---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: Compiling with Microsoft Visual C++


On 11.07.2016 16:05, racoon wrote:

On 10.07.2016 20:57, Georg Baum wrote:

If you want to help with 1), please do the following: Instead of
compiling
the INSTALL project, compile the LyX project that should be available
in the
solution as well. Then try to run LyX by pressing F5. Does that start
LyX?
Does the debugger show any errors? If it starts LyX, does LyX find
configure.py (it should be executaed automatically on he first start,
or if
you run it manually from the Tools menu). If configure.py is found,
are all
the usual document classes and modules available?


Did click on "Build" (is that the same as compile?) from the context
menu of "LyX" in the Solution Explorer. And it compiled with no errors.

Pressed F5, got a message about outdated files. Choose "Yes" to build
them. Got an error message (attached).


I guess I have to set LyX as my startup project (in the Solution
Explorer from the context menu of "LyX" choose "Set as StartUp
Project"). Before "ALL_BUILD" was the startup project.

Okay. After pressing F5 I get an error message for a missing Qt library
(attached) and LyX won't run...

Daniel



---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: Compiling with Microsoft Visual C++


On 10.07.2016 20:57, Georg Baum wrote:

If you want to help with 1), please do the following: Instead of compiling
the INSTALL project, compile the LyX project that should be available in the
solution as well. Then try to run LyX by pressing F5. Does that start LyX?
Does the debugger show any errors? If it starts LyX, does LyX find
configure.py (it should be executaed automatically on he first start, or if
you run it manually from the Tools menu). If configure.py is found, are all
the usual document classes and modules available?


Did click on "Build" (is that the same as compile?) from the context
menu of "LyX" in the Solution Explorer. And it compiled with no errors.

Pressed F5, got a message about outdated files. Choose "Yes" to build
them. Got an error message (attached).

Daniel



---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: Compiling with Microsoft Visual C++


On 11.07.2016 00:00, Kornel Benko wrote:

Am Sonntag, 10. Juli 2016 um 23:08:53, schrieb racoon 

I can't run LyX.exe in C:\LyX\lyx-23-build\LYX_INSTALLED\bin. It
complains about a mssing Qt5Svgd.dll.

Daniel



The target 'install' should put the .dll files into the same directory as 
LyX.exe.

Here, cross-compiled on linux, this directory shows:

iconengines  libwinpthread-1.dll  Qt5Concurrent.dll  
Qt5OpenGL.dllQt5WinExtras.dll
imageformats LyX.exe  Qt5Core.dll
Qt5PrintSupport.dll  tex2lyx.exe
libgcc_s_sjlj-1.dll  platformsQt5Gui.dll Qt5Svg.dll
libstdc++-6.dll  printsupport Qt5Network.dll 
Qt5Widgets.dll

Where are the .dll files on your system?


After choosing "Build" from the context menu of "INSTALL" (Solution
'LyX' > CMakeTargets) I get

LyX.exe
tex2lyx.exe

Daniel


---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: Compiling with Microsoft Visual C++

2016-07-10 Thread Kornel Benko

Am Sonntag, 10. Juli 2016 um 23:08:53, schrieb racoon 
> I can't run LyX.exe in C:\LyX\lyx-23-build\LYX_INSTALLED\bin. It 
> complains about a mssing Qt5Svgd.dll.
> 
> Daniel
> 

The target 'install' should put the .dll files into the same directory as 
LyX.exe.

Here, cross-compiled on linux, this directory shows:

iconengines  libwinpthread-1.dll  Qt5Concurrent.dll  
Qt5OpenGL.dllQt5WinExtras.dll
imageformats LyX.exe  Qt5Core.dll
Qt5PrintSupport.dll  tex2lyx.exe
libgcc_s_sjlj-1.dll  platformsQt5Gui.dll Qt5Svg.dll
libstdc++-6.dll  printsupport Qt5Network.dll 
Qt5Widgets.dll

Where are the .dll files on your system?

Kornel


signature.asc
Description: This is a digitally signed message part.

Re: Compiling with Microsoft Visual C++

2016-07-10 Thread racoon


On 10.07.2016 23:08, racoon wrote:

I can't run LyX.exe in C:\LyX\lyx-23-build\LYX_INSTALLED\bin. It
complains about a mssing Qt5Svgd.dll.


The LyX.exe complained about a couple of other missing Qt files.

Next I get the error messages attached.

Daniel

Re: Compiling with Microsoft Visual C++

2016-07-10 Thread racoon

I can't run LyX.exe in C:\LyX\lyx-23-build\LYX_INSTALLED\bin. It 
complains about a mssing Qt5Svgd.dll.


Daniel

Re: Compiling with Microsoft Visual C++

2016-07-10 Thread Georg Baum

racoon wrote:

> On 09.07.2016 17:33, racoon wrote:
>  > Next, I copy the dependencies. The culprit is, however, that there is
>  > no lyx.exe in
>  > C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\bin... so I
>  > can't execute it.
> 
> There are LyX.exe files in
> 
> C:\LyX\lyx-23-build\bin\Debug
> 
> and
> 
> C:\LyX\lyx-23-build\LYX_INSTALLED\bin
> 
> though. But I am not sure what to do with it.

The current installation instructions do not know of F5 or Ctrl-F5 in MSVC 
(although F5 is the most important reason to use MSVC and not mingw IMHO), 
so you are supposed to run LyX from C:\LyX\lyx-23-build\LYX_INSTALLED\bin. 
(to those who do not know MSVC: Ctrl-F5 starts the built executable, F5 
starts it in the debugger).

Many thanks for all your patience! I have incorporated all feedback in 
INSTALL.Win32. You did now execute all steps of the current installation 
instructions successfully. Now, I'd like to extend the instructions to make 
building LyX easier and less error prone in the future, and it would be very 
nice if you could help:

1) The most important step would be to get rid of the requirement to set 
LYX_INSTALL. This should only be needed for building an installer. Maybe 
this is only a matter of documentation, maybe the code in 
src/support/Package.cpp that handles all the path stuff for configuration 
files needs some adjustments for running from the build directory in MSVC.

2) Later some stuff like copying Qt dlls should be automated in cmake.

If you want to help with 1), please do the following: Instead of compiling 
the INSTALL project, compile the LyX project that should be available in the 
solution as well. Then try to run LyX by pressing F5. Does that start LyX? 
Does the debugger show any errors? If it starts LyX, does LyX find 
configure.py (it should be executaed automatically on he first start, or if 
you run it manually from the Tools menu). If configure.py is found, are all 
the usual document classes and modules available?

Georg

Re: Compiling with Microsoft Visual C++

2016-07-10 Thread Georg Baum

racoon wrote:

> Okay, next step taken, I think.
> 
> I set a couple of paths in CMAKE. Here is the "Show My Changes" output:
> 
> ---
> 
> Commandline options:
> -DLYX_USE_QT:STRING="QT5"
> -DQt5Widgets_DIR:PATH="C:\Qt\Qt5.6.1\5.6\msvc2015\lib\cmake\Qt5Widgets"
> -DLYX_DEPENDENCIES_DOWNLOAD:BOOL="1" -DLYX_INSTALL:BOOL="1"
> -DQt5Core_DIR:PATH="C:\Qt\Qt5.6.1\5.6\msvc2015\lib\cmake\Qt5Core"
> -DQT_QMAKE_EXECUTABLE:FILEPATH="C:/Qt/Qt5.6.1/5.6/msvc2015/bin/qmake.exe"
> -DCMAKE_PREFIX_PATH:PATH="C:/Qt/Qt5.6.1/5.6/msvc2015"
> -DLYX_INSTALL_PREFIX:PATH="C:/LyX/lyx-23-install"
> 
> 
> Cache file:
> LYX_USE_QT:STRING=QT5
> Qt5Widgets_DIR:PATH=C:\Qt\Qt5.6.1\5.6\msvc2015\lib\cmake\Qt5Widgets
> LYX_DEPENDENCIES_DOWNLOAD:BOOL=1
> LYX_INSTALL:BOOL=1
> Qt5Core_DIR:PATH=C:\Qt\Qt5.6.1\5.6\msvc2015\lib\cmake\Qt5Core
> QT_QMAKE_EXECUTABLE:FILEPATH=C:/Qt/Qt5.6.1/5.6/msvc2015/bin/qmake.exe
> CMAKE_PREFIX_PATH:PATH=C:/Qt/Qt5.6.1/5.6/msvc2015
> LYX_INSTALL_PREFIX:PATH=C:/LyX/lyx-23-install
> 
> ---
> 
> Not sure whether some of the settings are redundant.

Only LYX_USE_QT, LYX_DEPENDENCIES_DOWNLOAD and LYX_INSTALL should be needed. 
CMAKE_PREFIX_PATH does probably have no effect, it should be 
C:/Qt/Qt5.6.1/5.6/msvc2015/bin unless C:/Qt/Qt5.6.1/5.6/msvc2015/bin is 
already in the system path.


Georg

Re: Compiling with Microsoft Visual C++

2016-07-09 Thread Kornel Benko

Am Samstag, 9. Juli 2016 um 17:41:37, schrieb racoon 
> On 09.07.2016 17:33, racoon wrote:
>  > Next, I copy the dependencies. The culprit is, however, that there is no
>  > lyx.exe in
>  > C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\bin... so I
>  > can't execute it.
> 
> There are LyX.exe files in
> 
> C:\LyX\lyx-23-build\bin\Debug
> 
> and
> 
> C:\LyX\lyx-23-build\LYX_INSTALLED\bin

This is the correct installation place.
1.) You can make a .zip file from the directory  
"C:\LyX\lyx-23-build\LYX_INSTALLED".
2.) You can unzip it wherever you want.
I don't know how to proceed with registering on windows.

> though. But I am not sure what to do with it.
> 
> Daniel (Back on Sunday (GMT) evening the earliest)

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Compiling with Microsoft Visual C++

2016-07-09 Thread racoon


On 09.07.2016 17:33, racoon wrote:
> Next, I copy the dependencies. The culprit is, however, that there is no
> lyx.exe in
> C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\bin... so I
> can't execute it.

There are LyX.exe files in

C:\LyX\lyx-23-build\bin\Debug

and

C:\LyX\lyx-23-build\LYX_INSTALLED\bin

though. But I am not sure what to do with it.

Daniel (Back on Sunday (GMT) evening the earliest)

Re: Compiling with Microsoft Visual C++

2016-07-09 Thread racoon


Okay, next step taken, I think.

I set a couple of paths in CMAKE. Here is the "Show My Changes" output:

---

Commandline options:
-DLYX_USE_QT:STRING="QT5" 
-DQt5Widgets_DIR:PATH="C:\Qt\Qt5.6.1\5.6\msvc2015\lib\cmake\Qt5Widgets" 
-DLYX_DEPENDENCIES_DOWNLOAD:BOOL="1" -DLYX_INSTALL:BOOL="1" 
-DQt5Core_DIR:PATH="C:\Qt\Qt5.6.1\5.6\msvc2015\lib\cmake\Qt5Core" 
-DQT_QMAKE_EXECUTABLE:FILEPATH="C:/Qt/Qt5.6.1/5.6/msvc2015/bin/qmake.exe" 
-DCMAKE_PREFIX_PATH:PATH="C:/Qt/Qt5.6.1/5.6/msvc2015" 
-DLYX_INSTALL_PREFIX:PATH="C:/LyX/lyx-23-install"



Cache file:
LYX_USE_QT:STRING=QT5
Qt5Widgets_DIR:PATH=C:\Qt\Qt5.6.1\5.6\msvc2015\lib\cmake\Qt5Widgets
LYX_DEPENDENCIES_DOWNLOAD:BOOL=1
LYX_INSTALL:BOOL=1
Qt5Core_DIR:PATH=C:\Qt\Qt5.6.1\5.6\msvc2015\lib\cmake\Qt5Core
QT_QMAKE_EXECUTABLE:FILEPATH=C:/Qt/Qt5.6.1/5.6/msvc2015/bin/qmake.exe
CMAKE_PREFIX_PATH:PATH=C:/Qt/Qt5.6.1/5.6/msvc2015
LYX_INSTALL_PREFIX:PATH=C:/LyX/lyx-23-install

---

Not sure whether some of the settings are redundant.

Compiling in Visual Studio resulted in

== Build: 26 succeeded, 0 failed, 0 up-to-date, 0 skipped ==

Sounds good to me. Unfortunately, MSVC seems not to share my optimism 
and complains about a missing file (screen capture attached).


Nothing else happens.

What I noticed is that the directory C:\LyX\lyx-23-install is empty. 
Aren't there some files supposed to be or what is the directory for?


Next, I copy the dependencies. The culprit is, however, that there is no 
lyx.exe in 
C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\bin... so I 
can't execute it.


Maybe I am compiling it wrongly in MSVC? I just open the INSTALL project 
time in the explorer and hit STRG+F5.


(I think there are some typos in the INSTALL.Win32. I have attached 
corrections in brackets [].)


Daniel
Compiling LyX 2.3 for Win32 and creating Windows installer
==

It's recommended to compile LyX using Microsoft Visual C++ 2015 and CMake.


Compiling with Microsoft Visual C++
===

These instructions assume the LyX source code is in C:\LyX\lyx-23
You can also use another directory if you prefer.

1   Install MSVC 2015

If you don't have Visual C++ 2015 installed, get the free Community 
edition
from https://www.visualstudio.com/

2   Install Qt

Download the latest Qt for Open Source C++ development on Windows 
(VS2015)
from https://qt.io/download-open-source/
Qt 5.6.x is recommended, but 5.7.x or later versions should work as 
well.
Make sure that the bin subfolder of the Qt installation (e.g.
C:\Qt\Qt5.6.1\5.6\msvc2015\bin) is listed in the PATH environment 
variable.

3   Install Python

Install the latest Python 2.x or 3.x version from
https://www.python.org/downloads/

4   Install CMake

Install the latest CMake from http://www.cmake.org

5   Configure

- Open the "Developer Command Prompt for VS2015" from the
  "Visual Studio 2015\Visual Studio Tools" subfolder of the start menu.
  Run the CMake GUI from the command window that was opened.
  Alternatively, you can create a .bat file that first contains the line
  call "C:\Program Files (x86)\Microsoft Visual Studio 
14.0\VC\vcvarsall.bat" x86
  and then calls the CMake GUI and use this .bat file to start CMake.
  The MSVC 2015 command prompt or vcvarsall.bat set some environment
  variables that are needed for CMake to find the compiler.

- Set the source code path to C:\LyX\lyx-23
  Set the build path to C:\LyX\lyx-23-build
  Click Configure and set the generator to Visual Studio 14.

- Enable LYX_DEPENDENCIES_DOWNLOAD and click Configure.
  Pre-compiled dependencies will automatically be downloaded.

- Enable the LYX_INSTALL option, set CMAKE_INSTALL_PREFIX to
  C:\LyX\lyx-23-install and click Configure.

- Check the Advanced checkbox.
  Set GETTEXT_MSGFMT_EXECUTABLE to
  
C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\gettext-tools\msgfmt.exe,
  and do the same for the other gettext tools.

- Click Generate.

6   Compile

A Microsoft Visual C++ solution should have been generated at
C:\LyX\lyx-23-build\lyx.sln
Compile the INSTALL project to get a LyX installation in
C:\LyX\lyx-23-install

7   Copy dependencies

Copy
- C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\bin
- 
C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\imagemagick
- C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\python 
[Python?]
- 
C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\ghostscript
- C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\Resources
to C:\LyX\lyx-23-install

And

Re: Compiling with Microsoft Visual C++

2016-07-06 Thread racoon


On 06.07.2016 09:32, racoon wrote:

On 05.07.2016 21:46, Georg Baum wrote:

racoon wrote:


On 04.07.2016 09:11, racoon wrote:

"Compile the INSTALL project to get a LyX installation in
C:\LyX\lyx-23-install"

I guess it means opening "INSTALL.vcxproj" and STRG-F5. Getting

"Build: 14 succeeded, 12 failed, 0 up-to-date, 0 skipped"


Congratulations! You are almost there!


Can't run because of errors.


... And here are the errors from Visual Studio:



1>-- Build started: Project: lyx_version, Configuration: Debug Win32
--
2>-- Build started: Project: translations, Configuration: Debug
Win32 --
3>-- Build started: Project: check_ExternalTransforms,
Configuration: Debug Win32 --
1>  -- Git-hash = 6dfc255
1>  -- Created C:/LyX/lyx-23-build/lyx_date.tmp
1>  -- Created C:/LyX/lyx-23-build/lyx_commit_hash.tmp
4>-- Build started: Project: LyX (applications\LyX\LyX),
Configuration: Debug Win32 --
3>Qt5Cored.lib(Qt5Cored.dll) : fatal error LNK1112: module machine type
'x64' conflicts with target machine type 'X86'


You have a 64bit qt, but told cmake to create a 32bit target. You can
either
download a 32bit qt, or use the "Visual Studio 14 2015 Win64"
generator in
cmake instead of "Visual Studio 14 2015".

I am currently very busy, but I will look at your other reports in a few
days, update the build instructions and may come back to you with
questions.


Okay. The qt online installer did not download the x86 versions by
default. So I unchecked the x64 ones and added the x86 5.6.1 instead.

Unfortunately, cmake.exe crashes while compiling... Maybe some setting
was not correct in cmake because of the errors it generated?

Don't worry about delays. I have to do other things as well.


Here is the error log from Visual Studio:

---

1>  -- TOP_SRC_DIR = C:/LyX/lyx23
1>  --
1>  -- Building out-of-source
1>  --
1>  -- CXX11_FLAG_DETECTED = "noflagneeded"
1>  -- Compiler supports std_regex
1>CUSTOMBUILD : -- error : Could NOT find GNUWIN32, please set GNUWIN32_DIR
1>CUSTOMBUILD : -- error : or let cmake download all required files by 
using -DLYX_DEPENDENCIES_DOWNLOAD=1
1>  CMake Error at development/cmake/modules/FindGNUWIN32.cmake:43 
(message):

1>  Call Stack (most recent call first):
1>development/cmake/modules/LyXPaths.cmake:61 (find_package)
1>CMakeLists.txt:300 (include)
1>
1>
1>  -- Configuring incomplete, errors occurred!
1>  See also "C:/LyX/lyx-23-build/CMakeFiles/CMakeOutput.log".
1>  CMake Configure step failed.  Build files cannot be regenerated 
correctly.  Attempting to stop IDE build.

Re: Compiling with Microsoft Visual C++

2016-07-06 Thread racoon


On 05.07.2016 21:46, Georg Baum wrote:

racoon wrote:


On 04.07.2016 09:11, racoon wrote:

"Compile the INSTALL project to get a LyX installation in
C:\LyX\lyx-23-install"

I guess it means opening "INSTALL.vcxproj" and STRG-F5. Getting

"Build: 14 succeeded, 12 failed, 0 up-to-date, 0 skipped"


Congratulations! You are almost there!


Can't run because of errors.


... And here are the errors from Visual Studio:



1>-- Build started: Project: lyx_version, Configuration: Debug Win32
--
2>-- Build started: Project: translations, Configuration: Debug
Win32 --
3>-- Build started: Project: check_ExternalTransforms,
Configuration: Debug Win32 --
1>  -- Git-hash = 6dfc255
1>  -- Created C:/LyX/lyx-23-build/lyx_date.tmp
1>  -- Created C:/LyX/lyx-23-build/lyx_commit_hash.tmp
4>-- Build started: Project: LyX (applications\LyX\LyX),
Configuration: Debug Win32 --
3>Qt5Cored.lib(Qt5Cored.dll) : fatal error LNK1112: module machine type
'x64' conflicts with target machine type 'X86'


You have a 64bit qt, but told cmake to create a 32bit target. You can either
download a 32bit qt, or use the "Visual Studio 14 2015 Win64" generator in
cmake instead of "Visual Studio 14 2015".

I am currently very busy, but I will look at your other reports in a few
days, update the build instructions and may come back to you with questions.


Okay. The qt online installer did not download the x86 versions by 
default. So I unchecked the x64 ones and added the x86 5.6.1 instead.


Unfortunately, cmake.exe crashes while compiling... Maybe some setting 
was not correct in cmake because of the errors it generated?


Don't worry about delays. I have to do other things as well.

Daniel

Re: Compiling with Microsoft Visual C++

2016-07-05 Thread Georg Baum

racoon wrote:

> On 04.07.2016 09:11, racoon wrote:
>> "Compile the INSTALL project to get a LyX installation in
>> C:\LyX\lyx-23-install"
>>
>> I guess it means opening "INSTALL.vcxproj" and STRG-F5. Getting
>>
>> "Build: 14 succeeded, 12 failed, 0 up-to-date, 0 skipped"

Congratulations! You are almost there!

>> Can't run because of errors.
> 
> ... And here are the errors from Visual Studio:
> 
> 
> 
> 1>-- Build started: Project: lyx_version, Configuration: Debug Win32
> --
> 2>-- Build started: Project: translations, Configuration: Debug
> Win32 --
> 3>-- Build started: Project: check_ExternalTransforms,
> Configuration: Debug Win32 --
> 1>  -- Git-hash = 6dfc255
> 1>  -- Created C:/LyX/lyx-23-build/lyx_date.tmp
> 1>  -- Created C:/LyX/lyx-23-build/lyx_commit_hash.tmp
> 4>-- Build started: Project: LyX (applications\LyX\LyX),
> Configuration: Debug Win32 --
> 3>Qt5Cored.lib(Qt5Cored.dll) : fatal error LNK1112: module machine type
> 'x64' conflicts with target machine type 'X86'

You have a 64bit qt, but told cmake to create a 32bit target. You can either 
download a 32bit qt, or use the "Visual Studio 14 2015 Win64" generator in 
cmake instead of "Visual Studio 14 2015".

I am currently very busy, but I will look at your other reports in a few 
days, update the build instructions and may come back to you with questions.


Georg

Re: Compiling with Microsoft Visual C++

2016-07-05 Thread racoon


On 04.07.2016 09:11, racoon wrote:

"Compile the INSTALL project to get a LyX installation in
C:\LyX\lyx-23-install"

I guess it means opening "INSTALL.vcxproj" and STRG-F5. Getting

"Build: 14 succeeded, 12 failed, 0 up-to-date, 0 skipped"

Can't run because of errors.


... And here are the errors from Visual Studio:



1>-- Build started: Project: lyx_version, Configuration: Debug Win32 
--
2>-- Build started: Project: translations, Configuration: Debug 
Win32 --
3>-- Build started: Project: check_ExternalTransforms, 
Configuration: Debug Win32 --

1>  -- Git-hash = 6dfc255
1>  -- Created C:/LyX/lyx-23-build/lyx_date.tmp
1>  -- Created C:/LyX/lyx-23-build/lyx_commit_hash.tmp
4>-- Build started: Project: LyX (applications\LyX\LyX), 
Configuration: Debug Win32 --
3>Qt5Cored.lib(Qt5Cored.dll) : fatal error LNK1112: module machine type 
'x64' conflicts with target machine type 'X86'
5>-- Build started: Project: check_Length, Configuration: Debug 
Win32 --
5>Qt5Cored.lib(Qt5Cored.dll) : fatal error LNK1112: module machine type 
'x64' conflicts with target machine type 'X86'
6>-- Build started: Project: check_ListingsCaption, Configuration: 
Debug Win32 --
6>Qt5Cored.lib(Qt5Cored.dll) : fatal error LNK1112: module machine type 
'x64' conflicts with target machine type 'X86'
7>-- Build started: Project: check_filetools, Configuration: Debug 
Win32 --
7>Qt5Cored.lib(Qt5Cored.dll) : fatal error LNK1112: module machine type 
'x64' conflicts with target machine type 'X86'
8>-- Build started: Project: check_layout, Configuration: Debug 
Win32 --
8>Qt5Cored.lib(Qt5Cored.dll) : fatal error LNK1112: module machine type 
'x64' conflicts with target machine type 'X86'
9>-- Build started: Project: check_lstrings, Configuration: Debug 
Win32 --
9>Qt5Cored.lib(Qt5Cored.dll) : fatal error LNK1112: module machine type 
'x64' conflicts with target machine type 'X86'
10>-- Build started: Project: check_trivstring, Configuration: Debug 
Win32 --
10>Qt5Cored.lib(Qt5Cored.dll) : fatal error LNK1112: module machine type 
'x64' conflicts with target machine type 'X86'
11>-- Build started: Project: doc (doc\doc), Configuration: Debug 
Win32 --
12>-- Build started: Project: check_convert, Configuration: Debug 
Win32 --
12>Qt5Cored.lib(Qt5Cored.dll) : fatal error LNK1112: module machine type 
'x64' conflicts with target machine type 'X86'
13>-- Build started: Project: tex2lyx 
(applications\TeX2LyX\tex2lyx), Configuration: Debug Win32 --
13>Qt5Cored.lib(Qt5Cored.dll) : fatal error LNK1112: module machine type 
'x64' conflicts with target machine type 'X86'
4>Qt5Widgetsd.lib(Qt5Widgetsd.dll) : fatal error LNK1112: module machine 
type 'x64' conflicts with target machine type 'X86'
== Build: 3 succeeded, 10 failed, 13 up-to-date, 0 skipped 
==

Re: Compiling with Microsoft Visual C++

2016-07-04 Thread racoon


On 03.07.2016 18:48, racoon wrote:

[...]

So I guess CMake can't find my Qt5 installation?


Okay, for some reason LYX_USE_QT was set to QT4. I've changed it to QT5 
(I guess that should be the default, or?


By the way, are you sure about this:

"Enable the LYX_INSTALL option, set CMAKE_INSTALL_PREFIX to
C:\LyX\lyx-23-install and click Configure."?

CMake keeps resetting this PREFIX to LYX_INSTALLED.

Anyway, next errors in detail:

---

TOP_SRC_DIR = C:/LyX/lyx23

Building out-of-source

Using downloaded dependencies in C:/LyX/lyx-23-build/msvc2015-deps

CXX11_FLAG_DETECTED = "noflagneeded"
Compiler supports std_regex
Found GNUWIN32: C:/LyX/lyx-23-build/msvc2015-deps/lyx-windows-deps-msvc2015
Configuring NSIS files
NSIS files are created in C:/LyX/lyx-23-build/installer
CMake Error at CMakeLists.txt:591 (find_package):
  By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this 
project has
  asked CMake to find a package configuration file provided by 
"Qt5Core", but

  CMake did not find one.

  Could not find a package configuration file provided by "Qt5Core" 
with any

  of the following names:

Qt5CoreConfig.cmake
qt5core-config.cmake

  Add the installation prefix of "Qt5Core" to CMAKE_PREFIX_PATH or set
  "Qt5Core_DIR" to a directory containing one of the above files.  If
  "Qt5Core" provides a separate development package or SDK, be sure it has
  been installed.


Configuring incomplete, errors occurred!
See also "C:/LyX/lyx-23-build/CMakeFiles/CMakeOutput.log".

---

Daniel

Re: Compiling with Microsoft Visual C++

2016-07-03 Thread racoon


Okay. Couldn't give up yet. Finally, it kind of worked, I guess.

Uninstalled everything related to Visual Studio and ran CCleaner (just 
to be sure).


Here is what I had top do. You might want to add this to the INSTALL 
instructions:


- Installed Visual Studio (had to sign in with Microsoft since my trial 
period expired)


- Modify Visual Studio and add Visual C++ programming languages (in 
System settings > Programs) since it does not come with C++ 
pre-installed (could also be chosen during setup, I guess)


- Manually install "Windows Software Development Kit (SDK) für Windows 
8.1" from 
https://developer.microsoft.com/en-us/windows/downloads/windows-8-1-sdk



Now I have a new problem but that might be easier to fix:



TOP_SRC_DIR = C:/LyX/lyx23

Building out-of-source
The C compiler identification is MSVC 19.0.24210.0
The CXX compiler identification is MSVC 19.0.24210.0
Check for working C compiler using: Visual Studio 14 2015
Check for working C compiler using: Visual Studio 14 2015 -- works
Detecting C compiler ABI info
Detecting C compiler ABI info - done
Check for working CXX compiler using: Visual Studio 14 2015
Check for working CXX compiler using: Visual Studio 14 2015 -- works
Detecting CXX compiler ABI info
Detecting CXX compiler ABI info - done
Detecting CXX compile features
Detecting CXX compile features - done

CXX11_FLAG_DETECTED = "noflagneeded"
Compiler supports std_regex
Found CXX11Compiler: noflagneeded
ERROR: Could NOT find GNUWIN32, please set GNUWIN32_DIR
ERROR: or let cmake download all required files by using 
-DLYX_DEPENDENCIES_DOWNLOAD=1

CMake Error at development/cmake/modules/FindGNUWIN32.cmake:43 (message):
Call Stack (most recent call first):
  development/cmake/modules/LyXPaths.cmake:61 (find_package)
  CMakeLists.txt:300 (include)


Configuring incomplete, errors occurred!
See also "C:/LyX/lyx-23-build/CMakeFiles/CMakeOutput.log".



Anyway, now I had LYX_DEPENDENCIES_DOWNLOAD. Checked and configured 
again. Download seemed to have worked.


Next error message:



TOP_SRC_DIR = C:/LyX/lyx23

Building out-of-source

Using downloaded dependencies in C:/LyX/lyx-23-build/msvc2015-deps
Downloading lyx-windows-deps-msvc2015.zip ...
[download 0% complete]
[...]
[download 100% complete]

CXX11_FLAG_DETECTED = "noflagneeded"
Compiler supports std_regex
Found GNUWIN32: C:/LyX/lyx-23-build/msvc2015-deps/lyx-windows-deps-msvc2015
CMake Error at development/cmake/modules/FindQt4.cmake:1037 (message):
  Qt qmake not found!
Call Stack (most recent call first):
  CMakeLists.txt:619 (find_package)


Configuring incomplete, errors occurred!
See also "C:/LyX/lyx-23-build/CMakeFiles/CMakeOutput.log".



Went ahead anyway: Enabled the LYX_INSTALL option, set 
CMAKE_INSTALL_PREFIX to C:\LyX\lyx-23-install and clicked Configure.


Next error message:



TOP_SRC_DIR = C:/LyX/lyx23

Building out-of-source

Using downloaded dependencies in C:/LyX/lyx-23-build/msvc2015-deps

CXX11_FLAG_DETECTED = "noflagneeded"
Compiler supports std_regex
Found GNUWIN32: C:/LyX/lyx-23-build/msvc2015-deps/lyx-windows-deps-msvc2015
Configuring NSIS files
NSIS files are created in C:/LyX/lyx-23-build/installer
CMake Error at development/cmake/modules/FindQt4.cmake:1037 (message):
  Qt qmake not found!
Call Stack (most recent call first):
  CMakeLists.txt:619 (find_package)


Configuring incomplete, errors occurred!
See also "C:/LyX/lyx-23-build/CMakeFiles/CMakeOutput.log".



So I guess CMake can't find my Qt5 installation?

Also, I could not go ahead since GETTEXT_MSGFMT_EXECUTABLE was not 
selectable (even with Advanced checked).


Daniel
The system is: Windows - 6.1.7601 - AMD64
Compiling the C compiler identification source file "CMakeCCompilerId.c" 
succeeded.
Compiler:  
Build flags: 
Id flags: 

The output was:
0
Microsoft (R)-Buildmodul, Version 14.0.25420.1
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.

Der Buildvorgang wurde am 03.07.2016 18:37:22 gestartet.
Projekt "C:\LyX\lyx-23-build\CMakeFiles\3.5.2\CompilerIdC\CompilerIdC.vcxproj" 
auf Knoten "1" (Standardziele).
PrepareForBuild:
  Das Verzeichnis "Debug\" wird erstellt.
  Das Verzeichnis "Debug\CompilerIdC.tlog\" wird erstellt.
InitializeBuildStatus:
  "Debug\CompilerIdC.tlog\unsuccessfulbuild" wird erstellt, da "AlwaysCreate" 
angegeben wurde.
ClCompile:
  C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\CL.exe /c /nologo 
/W0 /WX- /Od /Oy- /D _MBCS /Gm- /EHsc /RTC1 /MDd /GS /fp:precise /Zc:wchar_t 
/Zc:forScope /Zc:inline /Fo"Debug\\" /Fd"Debug\vc140.pdb" /Gd /TC /analyze- 
/errorReport:queue CMakeCCompilerId.c
  CMakeCCompilerId.c
Link:
  C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\link.exe 
/ERRORREPORT:QUEUE /OUT:".\CompilerIdC.exe" /INCREMENTAL:NO /NOLOGO 
kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib 
shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /MANIFEST 
/MANIFESTUAC:"level='asInvoker' uiAccess='false'" /manifest:embed

Re: Compiling with Microsoft Visual C++

2016-06-30 Thread Georg Baum

racoon wrote:

> On 25.06.2016 20:41, Georg Baum wrote:
>>
>> This is strange. This file created the error in the CMakeError.log you
>> sent some days ago. Maybe this directory does not exist anymore after you
>> reinstalled the SDK? If the current CMakeError.log looks different than
>> the one you sent already please send this one, maybe the platform SDK
>> error is fixed and we see a different one now.
> 
> Sorry for the delay. Attached is the new error log.

No problem, it is not urgent.

Something has definitely changed from your last try. Now the file

C:\Microsoft.Cpp.Default.props

is missing. Searching for "Microsoft.Cpp.Default.props" in the cmake source 
code shows that this comes from a line

in the generated .vcxproj. $(VCTargetsPath) is a variable that should be set 
in the registry by the visual studio or windows sdk installer, a typical 
value is "C:\Program Files\MSBuild\". Therefore I am pretty sure that your 
MSVC and/or Windows SDK installation is botched. Unfortunately I have no 
idea how this happend or how to fix this.

Georg

Re: Compiling with Microsoft Visual C++

2016-06-30 Thread racoon


On 30.06.2016 14:18, Kornel Benko wrote:

I cannot judge about microsoft. But this looks like fundamental error.
What you can do is:
1.) create a simple CMakeLists.txt file with content

cmake_minimum_required(VERSION 2.6.4)
project(foo)

2.) call "cmake ."

The output should look somehow like this (on linux)
1.55 amd64.kornel 13:12 > cmake .
-- The C compiler identification is GNU 4.8.4
-- The CXX compiler identification is GNU 4.8.4
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /usr2/kornel/tmp/cmake

and post the errors to the cmake users list
"cm...@cmake.org" 


Mine looks like this:

-- Building for: Visual Studio 14 2015
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
CMake Error at CMakeLists.txt:2 (project):
  No CMAKE_C_COMPILER could be found.



CMake Error at CMakeLists.txt:2 (project):
  No CMAKE_CXX_COMPILER could be found.



-- Configuring incomplete, errors occurred!
See also "C:/LyX/CMakeFiles/CMakeOutput.log".
See also "C:/LyX/CMakeFiles/CMakeError.log".


I have to stop this project for a while. It seems just a bit too cumbersome.

Daniel

Re: Compiling with Microsoft Visual C++

2016-06-30 Thread Kornel Benko

Am Donnerstag, 30. Juni 2016 um 13:43:59, schrieb racoon 
> On 25.06.2016 20:41, Georg Baum wrote:
> > racoon wrote:
> >
> >> On 25.06.2016 18:16, Georg Baum wrote:
> >>>
> >>> You could also send me (privately please) the file C:\Program Files
> >>>
> > (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Platforms\Win32\PlatformToolsets\v140\Toolset.targets,
> >>> maybe I have then an idea about possible causes for the error message you
> >>> are seeing.
> >>
> >> I don't have a folder "Microsoft.Cpp" in
> >>
> >> C:\Program Files (x86)\MSBuild\
> >>
> >> I have a "Microsoft" folder there. But that does not contain any "v4.0"
> >> folder only "Windows Workflow Foundation".
> >
> > This is strange. This file created the error in the CMakeError.log you sent
> > some days ago. Maybe this directory does not exist anymore after you
> > reinstalled the SDK? If the current CMakeError.log looks different than the
> > one you sent already please send this one, maybe the platform SDK error is
> > fixed and we see a different one now.
> 
> Sorry for the delay. Attached is the new error log.
> 
> Daniel

I cannot judge about microsoft. But this looks like fundamental error.
What you can do is:
1.) create a simple CMakeLists.txt file with content

cmake_minimum_required(VERSION 2.6.4)
project(foo)

2.) call "cmake ."

The output should look somehow like this (on linux)
1.55 amd64.kornel 13:12 > cmake .
-- The C compiler identification is GNU 4.8.4
-- The CXX compiler identification is GNU 4.8.4
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /usr2/kornel/tmp/cmake

and post the errors to the cmake users list
"cm...@cmake.org" 

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Compiling with Microsoft Visual C++

2016-06-30 Thread racoon

On 25.06.2016 20:41, Georg Baum wrote:

racoon wrote:

On 25.06.2016 18:16, Georg Baum wrote:

You could also send me (privately please) the file C:\Program Files

(x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Platforms\Win32\PlatformToolsets\v140\Toolset.targets,

maybe I have then an idea about possible causes for the error message you
are seeing.

I don't have a folder "Microsoft.Cpp" in

C:\Program Files (x86)\MSBuild\

I have a "Microsoft" folder there. But that does not contain any "v4.0"
folder only "Windows Workflow Foundation".

This is strange. This file created the error in the CMakeError.log you sent
some days ago. Maybe this directory does not exist anymore after you
reinstalled the SDK? If the current CMakeError.log looks different than the
one you sent already please send this one, maybe the platform SDK error is
fixed and we see a different one now.

Sorry for the delay. Attached is the new error log.

Daniel

Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
Compiler:
Build flags:
Id flags:

The output was:
1
Microsoft (R)-Buildmodul, Version 4.6.1055.0
[Microsoft .NET Framework, Version 4.0.30319.42000]
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.

Der Buildvorgang wurde am 30.06.2016 13:42:19 gestartet.
Projekt "C:\LyX\lyx-23-build\CMakeFiles\3.5.2\CompilerIdC\CompilerIdC.vcxproj"
auf Knoten "1" (Standardziele).
C:\LyX\lyx-23-build\CMakeFiles\3.5.2\CompilerIdC\CompilerIdC.vcxproj(18,3):
error MSB4019: Das importierte Projekt "C:\Microsoft.Cpp.Default.props" wurde
nicht gefunden. Vergewissern Sie sich, dass der Pfad in der
-Deklaration korrekt und die Datei auf dem Datentrger vorhanden ist.
Die Erstellung des Projekts
"C:\LyX\lyx-23-build\CMakeFiles\3.5.2\CompilerIdC\CompilerIdC.vcxproj" ist
abgeschlossen (Standardziele) -- FEHLER.

Fehler beim Buildvorgang.

"C:\LyX\lyx-23-build\CMakeFiles\3.5.2\CompilerIdC\CompilerIdC.vcxproj"
(Standardziel) (1) ->
C:\LyX\lyx-23-build\CMakeFiles\3.5.2\CompilerIdC\CompilerIdC.vcxproj(18,3):
error MSB4019: Das importierte Projekt "C:\Microsoft.Cpp.Default.props" wurde
nicht gefunden. Vergewissern Sie sich, dass der Pfad in der
-Deklaration korrekt und die Datei auf dem Datentrger vorhanden ist.

0 Warnung(en)
1 Fehler

Verstrichene Zeit 00:00:00.06

Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp"
failed.
Compiler:
Build flags:
Id flags:

The output was:
1
Microsoft (R)-Buildmodul, Version 4.6.1055.0
[Microsoft .NET Framework, Version 4.0.30319.42000]
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.

Der Buildvorgang wurde am 30.06.2016 13:42:20 gestartet.
Projekt
"C:\LyX\lyx-23-build\CMakeFiles\3.5.2\CompilerIdCXX\CompilerIdCXX.vcxproj" auf
Knoten "1" (Standardziele).
C:\LyX\lyx-23-build\CMakeFiles\3.5.2\CompilerIdCXX\CompilerIdCXX.vcxproj(18,3):
error MSB4019: Das importierte Projekt "C:\Microsoft.Cpp.Default.props" wurde
nicht gefunden. Vergewissern Sie sich, dass der Pfad in der
-Deklaration korrekt und die Datei auf dem Datentrger vorhanden ist.
Die Erstellung des Projekts
"C:\LyX\lyx-23-build\CMakeFiles\3.5.2\CompilerIdCXX\CompilerIdCXX.vcxproj" ist
abgeschlossen (Standardziele) -- FEHLER.

Fehler beim Buildvorgang.

"C:\LyX\lyx-23-build\CMakeFiles\3.5.2\CompilerIdCXX\CompilerIdCXX.vcxproj"
(Standardziel) (1) ->

C:\LyX\lyx-23-build\CMakeFiles\3.5.2\CompilerIdCXX\CompilerIdCXX.vcxproj(18,3):
error MSB4019: Das importierte Projekt "C:\Microsoft.Cpp.Default.props" wurde
nicht gefunden. Vergewissern Sie sich, dass der Pfad in der
-Deklaration korrekt und die Datei auf dem Datentrger vorhanden ist.

0 Warnung(en)
1 Fehler

Verstrichene Zeit 00:00:00.06

Re: Compiling with Microsoft Visual C++

2016-06-25 Thread Georg Baum

racoon wrote:

> On 25.06.2016 18:16, Georg Baum wrote:
>>
>> You could also send me (privately please) the file C:\Program Files
>> 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Platforms\Win32\PlatformToolsets\v140\Toolset.targets,
>> maybe I have then an idea about possible causes for the error message you
>> are seeing.
> 
> I don't have a folder "Microsoft.Cpp" in
> 
> C:\Program Files (x86)\MSBuild\
> 
> I have a "Microsoft" folder there. But that does not contain any "v4.0"
> folder only "Windows Workflow Foundation".

This is strange. This file created the error in the CMakeError.log you sent 
some days ago. Maybe this directory does not exist anymore after you 
reinstalled the SDK? If the current CMakeError.log looks different than the 
one you sent already please send this one, maybe the platform SDK error is 
fixed and we see a different one now.

Georg

Re: Compiling with Microsoft Visual C++

2016-06-25 Thread racoon

On 25.06.2016 18:16, Georg Baum wrote:

racoon wrote:

Thanks for the sustained support!

You are welcome! I do it because building LyX on windows should be as easy
as it is on unix. Unfortunately this is not yet the case, and your help in
trying out different tests is appreciated as well.

On 21.06.2016 22:02, Georg Baum wrote:

The standalone SDK should be installed below C:\Program Files\Microsoft
SDKs\ or C:\Program Files (x86)\Windows Kits\. If there is nothing below
one of these folders then it is probably not installed.

Have the C:\Program Files (x86)\Windows Kits\ folder with content.

Unfortunately the SDK stuff is quite confusing. Sometimes the SDK is
included with MSVC, sometimes you need a standalone version. After some
googling it looks like MSVC 2015 comes with a newer SDK that should be
used, but the installion is optional. Some more things you could try:

- Make sure the MSVC included SDK is installed, as described at
http://stackoverflow.com/questions/31619296/cmake-does-not-find-visual-c-compiler.
Then create the MSVC project files with cmake again.

Tried (but also had the cl.exe before). Did not help.

- In contrast to my earlier advice, select MSVC 2010 in cmake as
generator, and have MSVC convert the projects during loading (this would
help in case there is a MSVC 2015 related bug in cmake).

Still same error.

Sorry, then I am out of ides for now. Kornel sent a message in another
thread pointing to
http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/55645. Did
you see it? Maybe asking on the cmake list gets some usable answers.

You could also send me (privately please) the file C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Platforms\Win32\PlatformToolsets\v140\Toolset.targets,
maybe I have then an idea about possible causes for the error message you
are seeing.

I don't have a folder "Microsoft.Cpp" in

C:\Program Files (x86)\MSBuild\

I have a "Microsoft" folder there. But that does not contain any "v4.0"
folder only "Windows Workflow Foundation".

Daniel

Re: Compiling with Microsoft Visual C++

2016-06-25 Thread Georg Baum

racoon wrote:

> Thanks for the sustained support!

You are welcome! I do it because building LyX on windows should be as easy 
as it is on unix. Unfortunately this is not yet the case, and your help in 
trying out different tests is appreciated as well.

> On 21.06.2016 22:02, Georg Baum wrote:
>> The standalone SDK should be installed below C:\Program Files\Microsoft
>> SDKs\ or C:\Program Files (x86)\Windows Kits\. If there is nothing below
>> one of these folders then it is probably not installed.
> 
> Have the C:\Program Files (x86)\Windows Kits\ folder with content.
> 
>> Unfortunately the SDK stuff is quite confusing. Sometimes the SDK is
>> included with MSVC, sometimes you need a standalone version. After some
>> googling it looks like MSVC 2015 comes with a newer SDK that should be
>> used, but the installion is optional. Some more things you could try:
>>
>> - Make sure the MSVC included SDK is installed, as described at
>> http://stackoverflow.com/questions/31619296/cmake-does-not-find-visual-c-compiler.
>> Then create the MSVC project files with cmake again.
> 
> Tried (but also had the cl.exe before). Did not help.
> 
>> - In contrast to my earlier advice, select MSVC 2010 in cmake as
>> generator, and have MSVC convert the projects during loading (this would
>> help in case there is a MSVC 2015 related bug in cmake).
> 
> Still same error.

Sorry, then I am out of ides for now. Kornel sent a message in another 
thread pointing to 
http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/55645. Did 
you see it? Maybe asking on the cmake list gets some usable answers.

You could also send me (privately please) the file C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Platforms\Win32\PlatformToolsets\v140\Toolset.targets,

maybe I have then an idea about possible causes for the error message you 
are seeing.

Georg

Re: Compiling with Microsoft Visual C++

2016-06-22 Thread racoon


Thanks for the sustained support!

On 21.06.2016 22:02, Georg Baum wrote:

The standalone SDK should be installed below C:\Program Files\Microsoft
SDKs\ or C:\Program Files (x86)\Windows Kits\. If there is nothing below one
of these folders then it is probably not installed.


Have the C:\Program Files (x86)\Windows Kits\ folder with content.


Unfortunately the SDK stuff is quite confusing. Sometimes the SDK is
included with MSVC, sometimes you need a standalone version. After some
googling it looks like MSVC 2015 comes with a newer SDK that should be used,
but the installion is optional. Some more things you could try:

- Make sure the MSVC included SDK is installed, as described at
http://stackoverflow.com/questions/31619296/cmake-does-not-find-visual-c-compiler.
 Then create the MSVC project files with cmake again.


Tried (but also had the cl.exe before). Did not help.


- In contrast to my earlier advice, select MSVC 2010 in cmake as generator,
and have MSVC convert the projects during loading (this would help in case
there is a MSVC 2015 related bug in cmake).


Still same error.

Daniel

Re: Compiling with Microsoft Visual C++

2016-06-21 Thread Georg Baum

racoon wrote:

> On 20.06.2016 22:10, Georg Baum wrote:
>>
>> Good, that brings us a step further. I assume you have the Windows
>> Platform SDK installed? If not, please install it from
>> https://developer.microsoft.com/en-us/windows/downloads/windows-8-1-sdk
>> and try again. If it is installed, it might be broken:
>> http://stackoverflow.com/questions/22188919/windows-sdk-registry-variable-not-found/25466317
>> contains some hints how to repair a broken SDK installation. It might
>> also be a cmake problem (although I doubt that), since a user had exactly
>> the same issue with a cmake project here:
>> http://stackoverflow.com/questions/36362469/cmake-does-not-find-windows-sdk-8-1
> 
> I could not find the SDK in installed programs. So I installed it. But
> it still does not work. Same error. And I still can't find the SDK under
> programs. Perhaps they are somewhere else to be found?

The standalone SDK should be installed below C:\Program Files\Microsoft 
SDKs\ or C:\Program Files (x86)\Windows Kits\. If there is nothing below one 
of these folders then it is probably not installed.

Unfortunately the SDK stuff is quite confusing. Sometimes the SDK is 
included with MSVC, sometimes you need a standalone version. After some 
googling it looks like MSVC 2015 comes with a newer SDK that should be used, 
but the installion is optional. Some more things you could try:

- Make sure the MSVC included SDK is installed, as described at 
http://stackoverflow.com/questions/31619296/cmake-does-not-find-visual-c-compiler.
 Then create the MSVC project files with cmake again.
- In contrast to my earlier advice, select MSVC 2010 in cmake as generator, 
and have MSVC convert the projects during loading (this would help in case 
there is a MSVC 2015 related bug in cmake).


Georg

Re: Compiling with Microsoft Visual C++

2016-06-21 Thread racoon


On 20.06.2016 22:10, Georg Baum wrote:

On 20.06.2016 10:14, racoon wrote:

On 19.06.2016 20:02, Georg Baum wrote:


Yes. Does cmake still not recognize the compiler if you call it from
that command window? In that case please send the CMakeError.log and
CMakeOutput.log files created by cmake, this would probably mean we
need to
change our cmake compiler detection.


Yes, no recognition still. Files attached.


Good, that brings us a step further. I assume you have the Windows Platform
SDK installed? If not, please install it from
https://developer.microsoft.com/en-us/windows/downloads/windows-8-1-sdk and
try again. If it is installed, it might be broken:
http://stackoverflow.com/questions/22188919/windows-sdk-registry-variable-not-found/25466317
 contains some hints how to repair a broken SDK
installation. It might also be a cmake problem (although I doubt that),
since a user had exactly the same issue with a cmake project here:
http://stackoverflow.com/questions/36362469/cmake-does-not-find-windows-sdk-8-1


I could not find the SDK in installed programs. So I installed it. But 
it still does not work. Same error. And I still can't find the SDK under 
programs. Perhaps they are somewhere else to be found?


Daniel

Re: Compiling with Microsoft Visual C++

2016-06-20 Thread Georg Baum

racoon wrote:

> On 20.06.2016 10:14, racoon wrote:
>> On 19.06.2016 20:02, Georg Baum wrote:
>>>
>>> Yes. Does cmake still not recognize the compiler if you call it from
>>> that command window? In that case please send the CMakeError.log and
>>> CMakeOutput.log files created by cmake, this would probably mean we
>>> need to
>>> change our cmake compiler detection.
>>
>> Yes, no recognition still. Files attached.

Good, that brings us a step further. I assume you have the Windows Platform 
SDK installed? If not, please install it from 
https://developer.microsoft.com/en-us/windows/downloads/windows-8-1-sdk and 
try again. If it is installed, it might be broken: 
http://stackoverflow.com/questions/22188919/windows-sdk-registry-variable-not-found/25466317
 contains some hints how to repair a broken SDK 
installation. It might also be a cmake problem (although I doubt that), 
since a user had exactly the same issue with a cmake project here: 
http://stackoverflow.com/questions/36362469/cmake-does-not-find-windows-sdk-8-1

> Just realized that they are partly in German. Hope that's not a problem.
> I don't know where to set another language. Both MSVC and CMake are
> already in English.

I speak German:-)

Georg

Re: Compiling with Microsoft Visual C++

2016-06-20 Thread racoon


On 20.06.2016 10:14, racoon wrote:

On 19.06.2016 20:02, Georg Baum wrote:

racoon wrote:


In a common command window cl is not found.


This is actually good. It means your PATH is not poisoned by specific
MSVC
tools.


But if I start

1) Open Developer Command Prompt for VS2015
2) call 'cl -v'

I get

Microsoft (R) C/C++ Optimizing Compiler Version 19.00.23918 for x86
Copyright (C) Microsoft Corporation.  All rights reserved.
cl : Command line warning D9002 : ignoring unknown option '-v'
cl : Command line error D8003 : missing source filename

So I guess that's okay.


Yes. Does cmake still not recognize the compiler if you call it from that
command window? In that case please send the CMakeError.log and
CMakeOutput.log files created by cmake, this would probably mean we
need to
change our cmake compiler detection.


Yes, no recognition still. Files attached.


Just realized that they are partly in German. Hope that's not a problem. 
I don't know where to set another language. Both MSVC and CMake are 
already in English.


Daniel

Re: Compiling with Microsoft Visual C++

2016-06-20 Thread racoon


On 19.06.2016 20:12, Kornel Benko wrote:

Am Sonntag, 19. Juni 2016 um 19:52:25, schrieb racoon 

On 19.06.2016 19:36, Kornel Benko wrote:

Am Sonntag, 19. Juni 2016 um 19:23:14, schrieb racoon 

On 19.06.2016 18:20, Georg Baum wrote:

racoon wrote:


...



The most important question now is why cmake does not find your C compiler.


I have no clue. There is a cl.exe in

C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin


Daniel, please check if you have cl.exe in PATH.
1.) Open a command window.
2.) call 'cl -v'


In a common command window cl is not found.

But if I start

1) Open Developer Command Prompt for VS2015
2) call 'cl -v'

I get

Microsoft (R) C/C++ Optimizing Compiler Version 19.00.23918 for x86
Copyright (C) Microsoft Corporation.  All rights reserved.
cl : Command line warning D9002 : ignoring unknown option '-v'
cl : Command line error D8003 : missing source filename

So I guess that's okay.


Alternatively you can specify the compiler via
-DCMAKE_CXX_COMPILER="C:\Program Files (x86)\Microsoft Visual Studio 
14.0\VC\bin/cl.exe"


Not sure what that means. I tried

cmake-gui.exe -DCMAKE_CXX_COMPILER="C:\Program Files (x86)\Microsoft
Visual Studio 14.0\VC\bin/cl.exe"


The parameter was meant for 'cmake', not for 'cmake-gui'.


but probably there was a typo so I tried


Cmake and most other window programs understand '/' IMHO.


cmake-gui.exe -DCMAKE_CXX_COMPILER="C:\Program Files (x86)\Microsoft
Visual Studio 14.0\VC\bin\cl.exe"

Same problem.


or set CMAKE_CXX_COMPILER in cmake-gui.


So where how do I do that exactly? I tried to "+ Add Entry" and

Name: CMAKE_CXX_COMPILER
Type: FILEPATH
Value: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\cl.exe


I would try to use '/' everywhere.
You may click on the button '...' near the file-path-value and select the 
compiler from the dialog.


Tried both in the cmake-gui.exe. Same errors.

If I should try cmake.exe instead I could make use of more instructions 
on how to use it. But I guess it would be the same result.

Re: Compiling with Microsoft Visual C++

2016-06-20 Thread racoon


On 19.06.2016 20:02, Georg Baum wrote:

racoon wrote:


In a common command window cl is not found.


This is actually good. It means your PATH is not poisoned by specific MSVC
tools.


But if I start

1) Open Developer Command Prompt for VS2015
2) call 'cl -v'

I get

Microsoft (R) C/C++ Optimizing Compiler Version 19.00.23918 for x86
Copyright (C) Microsoft Corporation.  All rights reserved.
cl : Command line warning D9002 : ignoring unknown option '-v'
cl : Command line error D8003 : missing source filename

So I guess that's okay.


Yes. Does cmake still not recognize the compiler if you call it from that
command window? In that case please send the CMakeError.log and
CMakeOutput.log files created by cmake, this would probably mean we need to
change our cmake compiler detection.


Yes, no recognition still. Files attached.

Daniel

Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
Compiler:  
Build flags: 
Id flags: 

The output was:
1
Microsoft (R)-Buildmodul, Version 14.0.25123.0
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.

Der Buildvorgang wurde am 20.06.2016 09:18:22 gestartet.
Projekt 
"C:\Users\Daniel\LyX\LyX23-build\CMakeFiles\3.5.2\CompilerIdC\CompilerIdC.vcxproj"
 auf Knoten "1" (Standardziele).
C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Platforms\Win32\PlatformToolsets\v140\Toolset.targets(34,5):
 error MSB8036: The Windows SDK version 8.1 was not found. Install the required 
version of Windows SDK or change the SDK version in the project property pages 
or by right-clicking the solution and selecting "Retarget solution". 
[C:\Users\Daniel\LyX\LyX23-build\CMakeFiles\3.5.2\CompilerIdC\CompilerIdC.vcxproj]
Die Erstellung des Projekts 
"C:\Users\Daniel\LyX\LyX23-build\CMakeFiles\3.5.2\CompilerIdC\CompilerIdC.vcxproj"
 ist abgeschlossen (Standardziele) -- FEHLER.

Fehler beim Buildvorgang.

"C:\Users\Daniel\LyX\LyX23-build\CMakeFiles\3.5.2\CompilerIdC\CompilerIdC.vcxproj"
 (Standardziel) (1) ->
(Desktop_PlatformPrepareForBuild Ziel) -> 
  C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Platforms\Win32\PlatformToolsets\v140\Toolset.targets(34,5):
 error MSB8036: The Windows SDK version 8.1 was not found. Install the required 
version of Windows SDK or change the SDK version in the project property pages 
or by right-clicking the solution and selecting "Retarget solution". 
[C:\Users\Daniel\LyX\LyX23-build\CMakeFiles\3.5.2\CompilerIdC\CompilerIdC.vcxproj]

0 Warnung(en)
1 Fehler

Verstrichene Zeit 00:00:00.25


Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" 
failed.
Compiler:  
Build flags: 
Id flags: 

The output was:
1
Microsoft (R)-Buildmodul, Version 14.0.25123.0
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.

Der Buildvorgang wurde am 20.06.2016 09:18:23 gestartet.
Projekt 
"C:\Users\Daniel\LyX\LyX23-build\CMakeFiles\3.5.2\CompilerIdCXX\CompilerIdCXX.vcxproj"
 auf Knoten "1" (Standardziele).
C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Platforms\Win32\PlatformToolsets\v140\Toolset.targets(34,5):
 error MSB8036: The Windows SDK version 8.1 was not found. Install the required 
version of Windows SDK or change the SDK version in the project property pages 
or by right-clicking the solution and selecting "Retarget solution". 
[C:\Users\Daniel\LyX\LyX23-build\CMakeFiles\3.5.2\CompilerIdCXX\CompilerIdCXX.vcxproj]
Die Erstellung des Projekts 
"C:\Users\Daniel\LyX\LyX23-build\CMakeFiles\3.5.2\CompilerIdCXX\CompilerIdCXX.vcxproj"
 ist abgeschlossen (Standardziele) -- FEHLER.

Fehler beim Buildvorgang.

"C:\Users\Daniel\LyX\LyX23-build\CMakeFiles\3.5.2\CompilerIdCXX\CompilerIdCXX.vcxproj"
 (Standardziel) (1) ->
(Desktop_PlatformPrepareForBuild Ziel) -> 
  C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Platforms\Win32\PlatformToolsets\v140\Toolset.targets(34,5):
 error MSB8036: The Windows SDK version 8.1 was not found. Install the required 
version of Windows SDK or change the SDK version in the project property pages 
or by right-clicking the solution and selecting "Retarget solution". 
[C:\Users\Daniel\LyX\LyX23-build\CMakeFiles\3.5.2\CompilerIdCXX\CompilerIdCXX.vcxproj]

0 Warnung(en)
1 Fehler

Verstrichene Zeit 00:00:00.22


Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
Compiler:  
Build flags: 
Id flags: 

The output was:
1
Microsoft (R)-Buildmodul, Version 14.0.25123.0
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.

Der Buildvorgang wurde am 20.06.2016 09:20:42 gestartet.
Projekt 
"C:\Users\Daniel\LyX\LyX23-build\CMakeFiles\3.5.2\CompilerIdC\CompilerIdC.vcxproj"
 auf Knoten "1" (Standardziele).
C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Platforms\Win32\PlatformToolsets\v140\Toolset.targets(34,5):
 error MSB8036: The Windows SDK version 8.1 was not found. Install the required 
version of Windows SDK or change the SDK version in the project property pages 
or by right-clicking the

Re: Compiling with Microsoft Visual C++

Am Sonntag, 19. Juni 2016 um 19:52:25, schrieb racoon 
> On 19.06.2016 19:36, Kornel Benko wrote:
> > Am Sonntag, 19. Juni 2016 um 19:23:14, schrieb racoon 
> >> On 19.06.2016 18:20, Georg Baum wrote:
> >>> racoon wrote:
> >
> > ...
> >
> >>>
> >>> The most important question now is why cmake does not find your C 
> >>> compiler.
> >>
> >> I have no clue. There is a cl.exe in
> >>
> >> C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin
> >
> > Daniel, please check if you have cl.exe in PATH.
> > 1.) Open a command window.
> > 2.) call 'cl -v'
> 
> In a common command window cl is not found.
> 
> But if I start
> 
> 1) Open Developer Command Prompt for VS2015
> 2) call 'cl -v'
> 
> I get
> 
> Microsoft (R) C/C++ Optimizing Compiler Version 19.00.23918 for x86
> Copyright (C) Microsoft Corporation.  All rights reserved.
> cl : Command line warning D9002 : ignoring unknown option '-v'
> cl : Command line error D8003 : missing source filename
> 
> So I guess that's okay.
> 
> > Alternatively you can specify the compiler via
> > -DCMAKE_CXX_COMPILER="C:\Program Files (x86)\Microsoft Visual Studio 
> > 14.0\VC\bin/cl.exe"
> 
> Not sure what that means. I tried
> 
> cmake-gui.exe -DCMAKE_CXX_COMPILER="C:\Program Files (x86)\Microsoft 
> Visual Studio 14.0\VC\bin/cl.exe"

The parameter was meant for 'cmake', not for 'cmake-gui'.

> but probably there was a typo so I tried

Cmake and most other window programs understand '/' IMHO.

> cmake-gui.exe -DCMAKE_CXX_COMPILER="C:\Program Files (x86)\Microsoft 
> Visual Studio 14.0\VC\bin\cl.exe"
> 
> Same problem.
> 
> > or set CMAKE_CXX_COMPILER in cmake-gui.
> 
> So where how do I do that exactly? I tried to "+ Add Entry" and
> 
> Name: CMAKE_CXX_COMPILER
> Type: FILEPATH
> Value: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\cl.exe

I would try to use '/' everywhere.
You may click on the button '...' near the file-path-value and select the 
compiler from the dialog.

> No luck either.
> 
> Daniel

Kornel
Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Compiling with Microsoft Visual C++

racoon wrote:

> In a common command window cl is not found.

This is actually good. It means your PATH is not poisoned by specific MSVC 
tools.

> But if I start
> 
> 1) Open Developer Command Prompt for VS2015
> 2) call 'cl -v'
> 
> I get
> 
> Microsoft (R) C/C++ Optimizing Compiler Version 19.00.23918 for x86
> Copyright (C) Microsoft Corporation.  All rights reserved.
> cl : Command line warning D9002 : ignoring unknown option '-v'
> cl : Command line error D8003 : missing source filename
> 
> So I guess that's okay.

Yes. Does cmake still not recognize the compiler if you call it from that 
command window? In that case please send the CMakeError.log and 
CMakeOutput.log files created by cmake, this would probably mean we need to 
change our cmake compiler detection.

Georg

Re: Compiling with Microsoft Visual C++

Kornel Benko wrote:

> Am Sonntag, 19. Juni 2016 um 19:23:14, schrieb racoon 
>> On 19.06.2016 18:20, Georg Baum wrote:
>> > racoon wrote:
> 
> ...
> 
>> >
>> > The most important question now is why cmake does not find your C
>> > compiler.
>> 
>> I have no clue. There is a cl.exe in
>> 
>> C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin

Then your MSVC installation is OK.

> Daniel, please check if you have cl.exe in PATH.
> 1.) Open a command window.
> 2.) call 'cl -v'

Having it in PATH is not recommended for MSVC, because you need different 
versions depending on whether you want to compile for 32bit or 64bit, and 
you can install different MSVC versions in parallel. Therefore MSVC supplies 
the batch file vcvarsall.bat which sets the correct paths. Any program that 
needs the MSVC tools in PATH should always be executed after this batch file 
was called (in the same command window or from the .bat file that calls 
vcvarsall.bat). MSVC does also create a start menu entry which opens a 
command prompt with that file already executed, so the instructions above 
should read:

1.) Open the "Developer Command Prompt for VS2015" from the "Visual Studio 
2015\Visual Studio Tools" subfolder of the start menu
2.) type 'cl -v' in the command window that was opened by 1)

Alternatively, one could also call vcvarsall.bat manually (in case the above 
does not work for any reason):

1.) Open a command window.
2.) type 'call "C:\Program Files (x86)\Microsoft Visual Studio 
14.0\VC\vcvarsall.bat" x86'
3.) type 'cl -v'

The single quotes must not be typed in both cases, and the line break should 
be ignored as well.

Georg

Re: Compiling with Microsoft Visual C++


On 19.06.2016 19:36, Kornel Benko wrote:

Am Sonntag, 19. Juni 2016 um 19:23:14, schrieb racoon 

On 19.06.2016 18:20, Georg Baum wrote:

racoon wrote:


...



The most important question now is why cmake does not find your C compiler.


I have no clue. There is a cl.exe in

C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin


Daniel, please check if you have cl.exe in PATH.
1.) Open a command window.
2.) call 'cl -v'


In a common command window cl is not found.

But if I start

1) Open Developer Command Prompt for VS2015
2) call 'cl -v'

I get

Microsoft (R) C/C++ Optimizing Compiler Version 19.00.23918 for x86
Copyright (C) Microsoft Corporation.  All rights reserved.
cl : Command line warning D9002 : ignoring unknown option '-v'
cl : Command line error D8003 : missing source filename

So I guess that's okay.


Alternatively you can specify the compiler via
-DCMAKE_CXX_COMPILER="C:\Program Files (x86)\Microsoft Visual Studio 
14.0\VC\bin/cl.exe"


Not sure what that means. I tried

cmake-gui.exe -DCMAKE_CXX_COMPILER="C:\Program Files (x86)\Microsoft 
Visual Studio 14.0\VC\bin/cl.exe"


but probably there was a typo so I tried

cmake-gui.exe -DCMAKE_CXX_COMPILER="C:\Program Files (x86)\Microsoft 
Visual Studio 14.0\VC\bin\cl.exe"


Same problem.


or set CMAKE_CXX_COMPILER in cmake-gui.


So where how do I do that exactly? I tried to "+ Add Entry" and

Name: CMAKE_CXX_COMPILER
Type: FILEPATH
Value: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\cl.exe

No luck either.

Daniel

Re: Compiling with Microsoft Visual C++

Am Sonntag, 19. Juni 2016 um 19:23:14, schrieb racoon 
> On 19.06.2016 18:20, Georg Baum wrote:
> > racoon wrote:

...

> >
> > The most important question now is why cmake does not find your C compiler.
> 
> I have no clue. There is a cl.exe in
> 
> C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin

Daniel, please check if you have cl.exe in PATH.
1.) Open a command window.
2.) call 'cl -v'

Alternatively you can specify the compiler via
-DCMAKE_CXX_COMPILER="C:\Program Files (x86)\Microsoft Visual Studio 
14.0\VC\bin/cl.exe"
or set CMAKE_CXX_COMPILER in cmake-gui.

> Still CMake keeps complaining that
> 
> The C compiler identification is unknown
> The CXX compiler identification is unknown
> 
> Daniel

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Compiling with Microsoft Visual C++


On 19.06.2016 18:20, Georg Baum wrote:

racoon wrote:


On 19.06.2016 16:09, Georg Baum wrote:


If you use the paths listed in INSTASLL.Win32, then you would need to
unpack it in the folder C:\LyX\lyx-23-build\msvc2015-deps. This would
create a folder C:\LyX\lyx-23-build\lyx-windows-deps-msvc2015
(lyx-windows-deps- msvc2015 is the top level folder in the .zip archive).


Sorry, I got a bit lost. I have no clue where "master at
48fd76d4bfb99ee" is. Which INSTALL.Win32 are you referring to? (We are
working with different versions now, right?)


The latest that I changed in master. Meanwhile I changed it again, because
the qmake part was wrong (you need to add the Qt bin folder to the PATH
environment variable). You can always find the latest version at
http://www.lyx.org/trac/browser/lyxgit/INSTALL.Win32.


I should unpack paths?
Probably some compressed file under a path, right? At which path can I
find the compressed file?


http://ftp.lyx.de/LyX-Windows-Deps/lyx-windows-deps-msvc2015.zip

However, it might be that you do not need the dependencies at all. For
earlier verions they did also contain stuff like libiconv which is now
contained in the 3rdparty folder of our sources and automatically built
using cmake. I know that these dependencies are needed if you want to work
on the translations and/or want to build an installer, but I believe they
are not needed anymore for simple compilation.

I would suggest you try to continue without unpacked dependencies, and if
that works we'll change the instructions accordingly.

The most important question now is why cmake does not find your C compiler.


I have no clue. There is a cl.exe in

C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin

Still CMake keeps complaining that

The C compiler identification is unknown
The CXX compiler identification is unknown

Daniel

Re: Compiling with Microsoft Visual C++

racoon wrote:

> On 19.06.2016 16:09, Georg Baum wrote:
>>
>> If you use the paths listed in INSTASLL.Win32, then you would need to
>> unpack it in the folder C:\LyX\lyx-23-build\msvc2015-deps. This would
>> create a folder C:\LyX\lyx-23-build\lyx-windows-deps-msvc2015
>> (lyx-windows-deps- msvc2015 is the top level folder in the .zip archive).
> 
> Sorry, I got a bit lost. I have no clue where "master at
> 48fd76d4bfb99ee" is. Which INSTALL.Win32 are you referring to? (We are
> working with different versions now, right?)

The latest that I changed in master. Meanwhile I changed it again, because 
the qmake part was wrong (you need to add the Qt bin folder to the PATH 
environment variable). You can always find the latest version at 
http://www.lyx.org/trac/browser/lyxgit/INSTALL.Win32.

> I should unpack paths?
> Probably some compressed file under a path, right? At which path can I
> find the compressed file?

http://ftp.lyx.de/LyX-Windows-Deps/lyx-windows-deps-msvc2015.zip

However, it might be that you do not need the dependencies at all. For 
earlier verions they did also contain stuff like libiconv which is now 
contained in the 3rdparty folder of our sources and automatically built 
using cmake. I know that these dependencies are needed if you want to work 
on the translations and/or want to build an installer, but I believe they 
are not needed anymore for simple compilation.

I would suggest you try to continue without unpacked dependencies, and if 
that works we'll change the instructions accordingly.

The most important question now is why cmake does not find your C compiler.

Georg

Re: Compiling with Microsoft Visual C++


ps. Also just made a fresh cloned with git. Did not help either.

Re: Compiling with Microsoft Visual C++

On 19.06.2016 16:09, Georg Baum wrote:

racoon wrote:

On 19.06.2016 14:41, Georg Baum wrote:

Please try Visual Studio 14 instead (or however MSVC2015 is called in
cmake, 14 is the internal MSVC version corresponding to the 2015
release). MSVC 2015 can load MSVC 2010 solutions, but if cmake knows that
the result is to be used by MSVC 2015 then it might generate solutions
better suited to MSVC 2015.

Selected "Visual Studio 14 2015".

That looks good.

This is because the instructions are incomplete. You need to call the
vcvarsall.bat file provided by MSVC before calling the CMake GUI. I
described this in the latest instructions in master. You can get
http://www.lyx.org/trac/browser/lyxgit/INSTALL.Win32?rev=a88d1f023bcb and
follow this version, it applies to 2.2.x as well except the python
requirement: Python 2.x is required for LyX 2.2.x, for current master one
can also use Python 3.x.

Did run vcvarsall.bat before opening "CMake (cmake-gui) from the Start
menu. But still the same error.

Sorry, I should have been more precide. vcvarsall.bat only influences the
cmd session it is started from. Sou you would need to open a console, call
vcvarsall.bat, and then running Cmake GUI from the same console window
typing the command in (including the full path if the cmake installation is
not included in the PATH environment variable).

http://www.lyx.org/trac/browser/lyxgit/INSTALL.Win32?rev=a88d1f023bcb
refers to an alternative using the "MSVC 2015 command prompt".

In the start menu under "Visual Studio 2015\Visual Studio Tools" I found

- Developer Command Prompt for VS2015
- MSBuild Command Prompt for VS2015

I ran cmake-gui.exe from both prompts but the same problem occured.

The first one should be correct. I was thinking about the corresponding
entry in MSVC itself, but the way via start menu is even easier. Some
background information can be found here:
https://msdn.microsoft.com/en-us/library/f35ctcxw.aspx

And in a sub folder "Windows Desktop Command Prompts" i found

- VS2015 x64 ARM Cross Tools Command Prompt
- VS2015 x64 Native Tools Command Prompt
- VS2015 x64 x86 Cross Tools Command Prompt
- and the same with x64 replaced by x86 and vice versa

Should I try them?

I guess they won't work if the developer prompt did not work.

Configuring incomplete, errors occurred!
See also "C:/Users/Daniel/LyX/LyX22-build/CMakeFiles/CMakeOutput.log".
See also "C:/Users/Daniel/LyX/LyX22-build/CMakeFiles/CMakeError.log".
--

Still no "LYX_DEPENDENCIES_DOWNLOAD" option. Only a list with many
"CMAKE_..." entries.

The dependencies download is broken. I fixed it in master at
48fd76d4bfb99ee. Until this is fixed in the 2.2.x branch I suggest you
donwload them manually to the expected location.

I am not sure this problem is related to mine.

Yes, it is one step ahead;-) This means it does not help if you find the
switch: The cmake code that will be executed by enabling it is outdated and
won't find the dependencies.

And I also don't
understand the solution. What is the "expected location"?

If you use the paths listed in INSTASLL.Win32, then you would need to unpack
it in the folder C:\LyX\lyx-23-build\msvc2015-deps. This would create a
folder C:\LyX\lyx-23-build\lyx-windows-deps-msvc2015 (lyx-windows-deps-
msvc2015 is the top level folder in the .zip archive).

Sorry, I got a bit lost. I have no clue where "master at
48fd76d4bfb99ee" is. Which INSTALL.Win32 are you referring to? (We are
working with different versions now, right?) I should unpack paths?
Probably some compressed file under a path, right? At which path can I
find the compressed file?

An alternative to the configuration with the CMake GUI is to adapt the
build5-2015.bat batch file (again from master):

http://www.lyx.org/trac/browser/lyxgit/development/cmake/build5-2015.bat?rev=c7c9744368cfab

This might be easier, I guess you only need to adapt a few paths.

I'll look into this if you say my problem could be solved by this, okay?

I am not sure if this would solve your problems. It is your choice, both the
GUI version and the .bat version should work, but some people prefer
clicking through a GUI, and others prefer a scripted solution.

I am wondering whether Visual Studio has installed the components
necessary. How can I check whether there even is a c or cxx compiler?

There should be a cl.exe in the VC\bin subfolder of the MSVC installation
directory.

Georg

Re: Compiling with Microsoft Visual C++

Am Sonntag, 19. Juni 2016 um 16:43:25, schrieb Kornel Benko 
> Am Sonntag, 19. Juni 2016 um 16:30:10, schrieb Georg Baum 
> 
> > Kornel Benko wrote:
> > 
> > > Am Sonntag, 19. Juni 2016 um 13:52:02, schrieb Georg Baum
> > > 
> > >> 
> > >> OK, then we need to document that instead of QT_QMAKE_EXECUTABLE. What I
> > >> did not understand yet is how cmake finds Qt5CoreConfig.cmake. If I only
> > >> have $QTDIR/bin in $PATH then does cmake find $QTDIR/lib/cmake/*.cmake?
> > >> Or does cmake require $QTDIR to be set? Or something else?
> > >> 
> > > 
> > > Try 'qmake -query'. This should imply some answers.

I forgot to mention development/cmake/modules/FindQt4.cmake. This is our
module for QT4, where *we* use qmake. it is not valid for QT5.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Compiling with Microsoft Visual C++

Am Sonntag, 19. Juni 2016 um 16:30:10, schrieb Georg Baum 

> Kornel Benko wrote:
> 
> > Am Sonntag, 19. Juni 2016 um 13:52:02, schrieb Georg Baum
> > 
> >> 
> >> OK, then we need to document that instead of QT_QMAKE_EXECUTABLE. What I
> >> did not understand yet is how cmake finds Qt5CoreConfig.cmake. If I only
> >> have $QTDIR/bin in $PATH then does cmake find $QTDIR/lib/cmake/*.cmake?
> >> Or does cmake require $QTDIR to be set? Or something else?
> >> 
> > 
> > Try 'qmake -query'. This should imply some answers.
> 
> That would be a chicken-and-egg problem: Unless cmake has built-in qt 
> support any knowledge about qmake would need to come from the Qt cmake 
> module, which is supposed to be found by querying qmake... If cmake really 
> has built-in qt support then a Qt5CoreConfig.cmake module would not be 
> needed.

Exactly. Therefore I prefer setting PATH.

> > The 'find_package()' tries number of paths to find the appropriate
> > Qt5CoreConfig.cmake, searching cmake-module-paths, lib paths and also
> > going through the PATH variable.
> 
> I had a look at https://cmake.org/cmake/help/v3.5/command/find_package.html. 
> It is quite complicated (and intransparent IMHO), but there seems to be some 
> magic that does indeed guess from bin directories in the PATH to 
> corresponding lib/cmake directories. This seems to be used by 
> build5-2915.bat as well, so I adjusted INSTALL.Win32 accordingly.
> 
> 
> Georg

Thanks Georg.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Compiling with Microsoft Visual C++

Kornel Benko wrote:

> Am Sonntag, 19. Juni 2016 um 13:52:02, schrieb Georg Baum
> 
>> 
>> OK, then we need to document that instead of QT_QMAKE_EXECUTABLE. What I
>> did not understand yet is how cmake finds Qt5CoreConfig.cmake. If I only
>> have $QTDIR/bin in $PATH then does cmake find $QTDIR/lib/cmake/*.cmake?
>> Or does cmake require $QTDIR to be set? Or something else?
>> 
> 
> Try 'qmake -query'. This should imply some answers.

That would be a chicken-and-egg problem: Unless cmake has built-in qt 
support any knowledge about qmake would need to come from the Qt cmake 
module, which is supposed to be found by querying qmake... If cmake really 
has built-in qt support then a Qt5CoreConfig.cmake module would not be 
needed.

> The 'find_package()' tries number of paths to find the appropriate
> Qt5CoreConfig.cmake, searching cmake-module-paths, lib paths and also
> going through the PATH variable.

I had a look at https://cmake.org/cmake/help/v3.5/command/find_package.html. 
It is quite complicated (and intransparent IMHO), but there seems to be some 
magic that does indeed guess from bin directories in the PATH to 
corresponding lib/cmake directories. This seems to be used by 
build5-2915.bat as well, so I adjusted INSTALL.Win32 accordingly.

Georg

Re: Compiling with Microsoft Visual C++

racoon wrote:

> On 19.06.2016 14:41, Georg Baum wrote:
>>
>> Please try Visual Studio 14 instead (or however MSVC2015 is called in
>> cmake, 14 is the internal MSVC version corresponding to the 2015
>> release). MSVC 2015 can load MSVC 2010 solutions, but if cmake knows that
>> the result is to be used by MSVC 2015 then it might generate solutions
>> better suited to MSVC 2015.
> 
> Selected "Visual Studio 14 2015".

That looks good.

>> This is because the instructions are incomplete. You need to call the
>> vcvarsall.bat file provided by MSVC before calling the CMake GUI. I
>> described this in the latest instructions in master. You can get
>> http://www.lyx.org/trac/browser/lyxgit/INSTALL.Win32?rev=a88d1f023bcb and
>> follow this version, it applies to 2.2.x as well except the python
>> requirement: Python 2.x is required for LyX 2.2.x, for current master one
>> can also use Python 3.x.
> 
> Did run vcvarsall.bat before opening "CMake (cmake-gui) from the Start
> menu. But still the same error.

Sorry, I should have been more precide. vcvarsall.bat only influences the 
cmd session it is started from. Sou you would need to open a console, call 
vcvarsall.bat, and then running Cmake GUI from the same console window 
typing the command in (including the full path if the cmake installation is 
not included in the PATH environment variable).

> http://www.lyx.org/trac/browser/lyxgit/INSTALL.Win32?rev=a88d1f023bcb
> refers to an alternative using the "MSVC 2015 command prompt".
> 
> In the start menu under "Visual Studio 2015\Visual Studio Tools" I found
> 
> - Developer Command Prompt for VS2015
> - MSBuild Command Prompt for VS2015
> 
> I ran cmake-gui.exe from both prompts but the same problem occured.

The first one should be correct. I was thinking about the corresponding 
entry in MSVC itself, but the way via start menu is even easier. Some 
background information can be found here: 
https://msdn.microsoft.com/en-us/library/f35ctcxw.aspx

> And in a sub folder "Windows Desktop Command Prompts" i found
> 
> - VS2015 x64 ARM Cross Tools Command Prompt
> - VS2015 x64 Native Tools Command Prompt
> - VS2015 x64 x86 Cross Tools Command Prompt
> - and the same with x64 replaced by x86 and vice versa
> 
> Should I try them?

I guess they won't work if the developer prompt did not work.

>>> Configuring incomplete, errors occurred!
>>> See also "C:/Users/Daniel/LyX/LyX22-build/CMakeFiles/CMakeOutput.log".
>>> See also "C:/Users/Daniel/LyX/LyX22-build/CMakeFiles/CMakeError.log".
>>> --
>>>
>>> Still no "LYX_DEPENDENCIES_DOWNLOAD" option. Only a list with many
>>> "CMAKE_..." entries.
>>
>> The dependencies download is broken. I fixed it in master at
>> 48fd76d4bfb99ee. Until this is fixed in the 2.2.x branch I suggest you
>> donwload them manually to the expected location.
> 
> I am not sure this problem is related to mine.

Yes, it is one step ahead;-) This means it does not help if you find the 
switch: The cmake code that will be executed by enabling it is outdated and 
won't find the dependencies.

> And I also don't
> understand the solution. What is the "expected location"?

If you use the paths listed in INSTASLL.Win32, then you would need to unpack 
it in the folder C:\LyX\lyx-23-build\msvc2015-deps. This would create a 
folder C:\LyX\lyx-23-build\lyx-windows-deps-msvc2015 (lyx-windows-deps-
msvc2015 is the top level folder in the .zip archive).

>> An alternative to the configuration with the CMake GUI is to adapt the
>> build5-2015.bat batch file (again from master):
>> 
http://www.lyx.org/trac/browser/lyxgit/development/cmake/build5-2015.bat?rev=c7c9744368cfab
>>
>> This might be easier, I guess you only need to adapt a few paths.
> 
> I'll look into this if you say my problem could be solved by this, okay?

I am not sure if this would solve your problems. It is your choice, both the 
GUI version and the .bat version should work, but some people prefer 
clicking through a GUI, and others prefer a scripted solution.

> I am wondering whether Visual Studio has installed the components
> necessary. How can I check whether there even is a c or cxx compiler?

There should be a cl.exe in the VC\bin subfolder of the MSVC installation 
directory.

Georg

Re: Compiling with Microsoft Visual C++

On 19.06.2016 14:41, Georg Baum wrote:

racoon wrote:

Hi,

I'd like to compile LyX on my Win7 machine. However, I get errors when I
try to compile LyX even though I tried to follow the instruction step by
step. Maybe someone can help:

Unfortunately the instructions are outdated (details below). It would be
very nice if you could help us to improve them. While I have some MSVC
kowledge I have no machine with installd MSVC to test, so your input would
be very welcome.

I am happy to give feedback.

2 Install Qt

Download the latest Qt for Open Source C++ development on Windows
(VS2010) from http://qt-project.org/downloads

I got Qt 5.7.

Please report back how this works. To my knowledge you are the first one to
try Qt 5.7.

I will.

Click on Configure informs me that the build directory does not exist.
Creating.

and set the generator to Visual Studio 10.

Done.

Please try Visual Studio 14 instead (or however MSVC2015 is called in cmake,
14 is the internal MSVC version corresponding to the 2015 release). MSVC
2015 can load MSVC 2010 solutions, but if cmake knows that the result is to
be used by MSVC 2015 then it might generate solutions better suited to MSVC
2015.

Selected "Visual Studio 14 2015".

From the log:
--
TOP_SRC_DIR = C:/Users/Daniel/LyX/LyX22

Building out-of-source
The C compiler identification is unknown
The CXX compiler identification is unknown
CMake Error at CMakeLists.txt:76 (project):
No CMAKE_C_COMPILER could be found.

CMake Error at CMakeLists.txt:76 (project):
No CMAKE_CXX_COMPILER could be found.

Did run vcvarsall.bat before opening "CMake (cmake-gui) from the Start
menu. But still the same error.

http://www.lyx.org/trac/browser/lyxgit/INSTALL.Win32?rev=a88d1f023bcb
refers to an alternative using the "MSVC 2015 command prompt".

In the start menu under "Visual Studio 2015\Visual Studio Tools" I found

- Developer Command Prompt for VS2015
- MSBuild Command Prompt for VS2015

I ran cmake-gui.exe from both prompts but the same problem occured.

And in a sub folder "Windows Desktop Command Prompts" i found

- VS2015 x64 ARM Cross Tools Command Prompt
- VS2015 x64 Native Tools Command Prompt
- VS2015 x64 x86 Cross Tools Command Prompt
- and the same with x64 replaced by x86 and vice versa

Should I try them?

Configuring incomplete, errors occurred!
See also "C:/Users/Daniel/LyX/LyX22-build/CMakeFiles/CMakeOutput.log".
See also "C:/Users/Daniel/LyX/LyX22-build/CMakeFiles/CMakeError.log".
--

Still no "LYX_DEPENDENCIES_DOWNLOAD" option. Only a list with many
"CMAKE_..." entries.

The dependencies download is broken. I fixed it in master at
48fd76d4bfb99ee. Until this is fixed in the 2.2.x branch I suggest you
donwload them manually to the expected location.

I am not sure this problem is related to mine. And I also don't
understand the solution. What is the "expected location"?

An alternative to the configuration with the CMake GUI is to adapt the
build5-2015.bat batch file (again from master):
http://www.lyx.org/trac/browser/lyxgit/development/cmake/build5-2015.bat?rev=c7c9744368cfab

This might be easier, I guess you only need to adapt a few paths.

I'll look into this if you say my problem could be solved by this, okay?

I am wondering whether Visual Studio has installed the components
necessary. How can I check whether there even is a c or cxx compiler?

Daniel

Re: Compiling with Microsoft Visual C++

Am Sonntag, 19. Juni 2016 um 13:52:02, schrieb Georg Baum 

> Kornel Benko wrote:
> 
> > He claimed to have installed QT5.7.
> > We are using find_package(Qt5Core REQUIRED)
> > The module (not part of cmake but part of qt) is named
> > /Qt5CoreConfig.cmake. So it depends of where he installed his
> > QT and if he has the correct path set. It may be sufficient to know
> > qmake-path, I prefer to use also some other QT executables so I set the
> > PATH variable. (See moc, linguist, rcc, designer etc)
> 
> OK, then we need to document that instead of QT_QMAKE_EXECUTABLE. What I did 
> not understand yet is how cmake finds Qt5CoreConfig.cmake. If I only have 
> $QTDIR/bin in $PATH then does cmake find $QTDIR/lib/cmake/*.cmake? Or does 
> cmake require $QTDIR to be set? Or something else?
> 

Try 'qmake -query'. This should imply some answers.

The 'find_package()' tries number of paths to find the appropriate 
Qt5CoreConfig.cmake,
searching cmake-module-paths, lib paths and also going through the PATH 
variable.

> Georg

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Compiling with Microsoft Visual C++

Kornel Benko wrote:

> He claimed to have installed QT5.7.
> We are using find_package(Qt5Core REQUIRED)
> The module (not part of cmake but part of qt) is named
> /Qt5CoreConfig.cmake. So it depends of where he installed his
> QT and if he has the correct path set. It may be sufficient to know
> qmake-path, I prefer to use also some other QT executables so I set the
> PATH variable. (See moc, linguist, rcc, designer etc)

OK, then we need to document that instead of QT_QMAKE_EXECUTABLE. What I did 
not understand yet is how cmake finds Qt5CoreConfig.cmake. If I only have 
$QTDIR/bin in $PATH then does cmake find $QTDIR/lib/cmake/*.cmake? Or does 
cmake require $QTDIR to be set? Or something else?

Georg

Re: Compiling with Microsoft Visual C++

racoon wrote:

> Hi,
> 
> I'd like to compile LyX on my Win7 machine. However, I get errors when I
> try to compile LyX even though I tried to follow the instruction step by
> step. Maybe someone can help:

Unfortunately the instructions are outdated (details below). It would be 
very nice if you could help us to improve them. While I have some MSVC 
kowledge I have no machine with installd MSVC to test, so your input would 
be very welcome.

>> 2Install Qt
>>
>> Download the latest Qt for Open Source C++ development on Windows
>> (VS2010) from http://qt-project.org/downloads
> 
> I got Qt 5.7.

Please report back how this works. To my knowledge you are the first one to 
try Qt 5.7.

> Click on Configure informs me that the build directory does not exist.
> Creating.
> 
>> and set the generator to Visual Studio 10.
> 
> Done.

Please try Visual Studio 14 instead (or however MSVC2015 is called in cmake, 
14 is the internal MSVC version corresponding to the 2015 release). MSVC 
2015 can load MSVC 2010 solutions, but if cmake knows that the result is to 
be used by MSVC 2015 then it might generate solutions better suited to MSVC 
2015.

>  From the log:
> --
> TOP_SRC_DIR = C:/Users/Daniel/LyX/LyX22
> 
> Building out-of-source
> The C compiler identification is unknown
> The CXX compiler identification is unknown
> CMake Error at CMakeLists.txt:76 (project):
>No CMAKE_C_COMPILER could be found.
> 
> 
> 
> CMake Error at CMakeLists.txt:76 (project):
>No CMAKE_CXX_COMPILER could be found.

This is because the instructions are incomplete. You need to call the 
vcvarsall.bat file provided by MSVC before calling the CMake GUI. I 
described this in the latest instructions in master. You can get  
http://www.lyx.org/trac/browser/lyxgit/INSTALL.Win32?rev=a88d1f023bcb and 
follow this version, it applies to 2.2.x as well except the python 
requirement: Python 2.x is required for LyX 2.2.x, for current master one 
can also use Python 3.x.

> Configuring incomplete, errors occurred!
> See also "C:/Users/Daniel/LyX/LyX22-build/CMakeFiles/CMakeOutput.log".
> See also "C:/Users/Daniel/LyX/LyX22-build/CMakeFiles/CMakeError.log".
> --
> 
> Still no "LYX_DEPENDENCIES_DOWNLOAD" option. Only a list with many
> "CMAKE_..." entries.

The dependencies download is broken. I fixed it in master at 
48fd76d4bfb99ee. Until this is fixed in the 2.2.x branch I suggest you 
donwload them manually to the expected location.

An alternative to the configuration with the CMake GUI is to adapt the 
build5-2015.bat batch file (again from master): 
http://www.lyx.org/trac/browser/lyxgit/development/cmake/build5-2015.bat?rev=c7c9744368cfab

This might be easier, I guess you only need to adapt a few paths.

Georg

Re: Compiling with Microsoft Visual C++

Am Sonntag, 19. Juni 2016 um 13:11:55, schrieb Georg Baum 

> Kornel Benko wrote:
> 
> > Am Samstag, 18. Juni 2016 um 18:15:51, schrieb racoon 
> >> 
> >> > - Set QT_QMAKE_EXECUTABLE to e.g.
> >> > C:\Qt\qt-everywhere-opensource-src-4.8.4\bin\qmake.exe
> >> > and Configure again.
> > 
> > I think, this is important only if you use QT4
> 
> How is qt5 found then?
>

He claimed to have installed QT5.7.
We are using find_package(Qt5Core REQUIRED)
The module (not part of cmake but part of qt) is named 
/Qt5CoreConfig.cmake.
So it depends of where he installed his QT and if he has the correct path set.
It may be sufficient to know qmake-path, I prefer to use also some other QT 
executables so I set the PATH variable.
(See moc, linguist, rcc, designer etc)

> Georg

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Compiling with Microsoft Visual C++

Kornel Benko wrote:

> Am Samstag, 18. Juni 2016 um 18:15:51, schrieb racoon 
>> 
>> > - Set QT_QMAKE_EXECUTABLE to e.g.
>> > C:\Qt\qt-everywhere-opensource-src-4.8.4\bin\qmake.exe
>> > and Configure again.
> 
> I think, this is important only if you use QT4

How is qt5 found then?


Georg

Re: Compiling with Microsoft Visual C++

Am Sonntag, 19. Juni 2016 um 11:31:56, schrieb racoon 
> On 18.06.2016 23:09, Kornel Benko wrote:
> > Am Samstag, 18. Juni 2016 um 18:15:51, schrieb racoon 
> >> Hi,
> >>
> >> I'd like to compile LyX on my Win7 machine. However, I get errors when I
> >> try to compile LyX even though I tried to follow the instruction step by
> >> step. Maybe someone can help:
> >>
> >>> Compiling with Microsoft Visual C++
> >>> ===
> >>>
> >>>   These instructions assume the LyX source code is in C:\LyX\lyx-21
> >>>   You can also use another directory if you prefer.
> >>>
> >>> 1 Install MSVC 2010
> >>>
> >>>   If you don't have Visual C++ 2010 installed, get the free Express 
> >>> edition from
> >>>   http://www.microsoft.com/express/Downloads/
> >>>
> >>>   (All dependencies are linked against the MSVC 2010 runtime and won't 
> >>> work in
> >>>   combination with MSVC 2008. You'll get crashes and other unexpected 
> >>> issues.)
> >>
> >> I got MSVC 2015.
> >>
> >>> 2 Install Qt
> >>>
> >>>   Download the latest Qt for Open Source C++ development on Windows 
> >>> (VS2010)
> >>>   from http://qt-project.org/downloads
> >>
> >> I got Qt 5.7.
> >>
> >>> 3 Install Python
> >>>
> >>>   Install the latest Python 2.x version (not Python 3.x !) from
> >>>   http://www.python.org/download/
> >>
> >> I got Phython 2.7.11 (64/Bit)
> >>
> >>>
> >>> 4 Install CMake
> >>>
> >>>   Install the latest CMake from http://www.cmake.org
> >>
> >> I got CMake 3.5.2.
> >>
> >>> 5 Configure
> >>>
> >>>   - Run the CMake GUI.
> >>>   
> >>>   - Set the source code path to C:\LyX\lyx-21
> >>> Set the build path to C:\LyX\lyx-21-build
> >>
> >> Source code: C:/Users/Daniel/LyX/LyX22
> >> Build: C:/Users/Daniel/LyX/LyX22-Build
> >>
> >>> Click Configure
> >>
> >> Click on Configure informs me that the build directory does not exist.
> >> Creating.
> >>
> >>> and set the generator to Visual Studio 10.
> >>
> >> Done.
> >>
> >>>   - Enable LYX_DEPENDENCIES_DOWNLOAD and click Configure.
> >>
> >> Where? I don't see such an option. I am still in the CMakeSetup dialog.
> >
> > The first underline in a variable name specifies a group. That means you can
> > find LYX_DEPENDENCIES_DOWNLOAD in the group 'LYX'.
> > Open the group, e.g. click on the small triangle left to 'LYX'.
> 
> I don't see any groups in CMakeSetup dialog (attacked CMake2.png).

'Grouped' is not checked.
 
> >> Click "Finish" first? Doing.
> >>
> >> Error message: "Error in configuring process, project files may be 
> >> invalid."
> >>
> >>  From the log:
> >> --
> >> TOP_SRC_DIR = C:/Users/Daniel/LyX/LyX22
> >>
> >> Building out-of-source
> >> The C compiler identification is unknown
> >> The CXX compiler identification is unknown
> >
> > Looks like your c-compiler is not in PATH.
> 
> Okay. So is it not installed? How do I install it? I thought Visual 
> Studio would take care of this.
> 
> Or do I need to add something manually to PATH? If so what might that be?

Don't know what exactly to do on windows. I am on linux.
You are the windows expert from my POV.
As to what that might be: You have installed Visual Studio to some place, so 
you should know IMHO.

> >> CMake Error at CMakeLists.txt:76 (project):
> >>No CMAKE_C_COMPILER could be found.
> >>
> >>
> >>
> >> CMake Error at CMakeLists.txt:76 (project):
> >>No CMAKE_CXX_COMPILER could be found.
> >>
> >>
> >>
> >> Configuring incomplete, errors occurred!
> >> See also "C:/Users/Daniel/LyX/LyX22-build/CMakeFiles/CMakeOutput.log".
> >> See also "C:/Users/Daniel/LyX/LyX22-build/CMakeFiles/CMakeError.log".
> >> --
> >>
> >> Still no "LYX_DEPENDENCIES_DOWNLOAD" option. Only a list with many
> >> "CMAKE_..." entries.
> >>
> >>> Pre-compiled dependencies will automatically be downloaded.
> >>
> >> I don't think so...
> >>
> >>>   - Set QT_QMAKE_EXECUTABLE to e.g.
> >>> C:\Qt\qt-everywhere-opensource-src-4.8.4\bin\qmake.exe
> >>> and Configure again.
> >
> > I think, this is important only if you use QT4
> >
> >> Don't have that option either.
> >>
> >>>   - Enable the LYX_INSTALL option, set CMAKE_INSTALL_PREFIX to
> >>> C:\LyX\lyx-21-install and click Configure.
> >>
> >> No LYX_INSTALL option either. Setting CMAKE_INSTALL_PREFIX
> >> C:/Users/Daniel/LyX/LyX22-install.
> >
> > Are you sure, you want to install into this directory?
> 
> Why not?

It is your choice.

> >> Clicking Configure.
> >>
> >> Same error message as before: "Error in configuring process, project
> >> files may be invalid."
> >>
> >>>   - Check the Advanced checkbox.
> >>
> >> Is already checked.
> >>
> >>> Set GETTEXT_MSGFMT_EXECUTABLE to
> >>> C:\LyX\lyx-21-build\msvc2010-deps\deps20\gettext-tools\msgfmt.exe,
> >>> and do the same for the other gettext tools.
> >
> > Open group GETTEXT.
> 
> I still see only CMAKE_*'s (attacked CMake2.png).
> 

Because of missing c-compiler you don't see any variables depending on it.
First make sure you

Re: Compiling with Microsoft Visual C++