RE: [fltk.general] fltk-1.4 with cmake on windows [General Use]

[MacArthur, Ian (Leonardo, UK)]

> What you listed is exactly what I did, but to no success. Changing the
> architecture from win32 to x64, don't know why, looses many settings,
> which should be reset by hand -- in something like 80 projects. So I
> gave up.


Hmm; I do not really know - I can only say it seemed to work for me.

I selected the top level solution, then when I created the new architecture entry, it asked if I wanted to copy the settings from the WIN32 port (I did) and to update all the subprojects (I did) and then it did... stuff... took a while.
In the end, it pretty much seemed to work, as far as I can tell.

I'm not keen on VS, nor IDE's in general, so I can not claim this is the right way to go. Ask Microsoft!

For Windows builds, I generally use mingw32 or mingw64 and the stock autoconf-based fltk build system in an Msys shell, and that generally "Just Works" for all my stuff.




Leonardo MW Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL
A company registered in England & Wales. Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

[Albrecht Schlosser]

On 29.11.2016 10:51 MacArthur, Ian (Leonardo, UK) wrote:
>> What you listed is exactly what I did, but to no success. Changing the
>> architecture from win32 to x64, don't know why, looses many settings,
>> which should be reset by hand -- in something like 80 projects. So I
>> gave up.
>
>
> Hmm; I do not really know - I can only say it seemed to work for me.

I can confirm Daniele's experiences. I did the same, and it failed
miserably. I installed a patch / update of Visual Studio 2010 because it
seemed to lack 64-bit support entirely, but it didn't work after the
update. IIRC I got the same issue that "it" told me to update settings
by hand, and I gave up as well.

Whereas using CMake to generate the VS 2010 files with the 64-bit
toolset worked flawlessly, so I used this for testing.

[Ian MacArthur]

On Tue Nov 29 2016 11:41:34, Albrecht Schlosser wrote:
> On 29.11.2016 10:51 MacArthur, Ian (Leonardo, UK) wrote:
>>> What you listed is exactly what I did, but to no success. Changing the
>>> architecture from win32 to x64, don't know why, looses many settings,
>>> which should be reset by hand -- in something like 80 projects. So I
>>> gave up.
>>
>>
>> Hmm; I do not really know - I can only say it seemed to work for me.
>
> I can confirm Daniele's experiences. I did the same, and it failed miserably. I installed a patch / update of Visual Studio 2010 because it seemed to lack 64-bit support entirely, but it didn't work after the update. IIRC I got the same issue that "it" told me to update settings by hand, and I gave up as well.

OK; I used the VS 2015 Community version, and once I clicked through the dialogs it spent quite a while doing *something* then I ended up with a solution that appeared to work. Maybe I just got lucky?

I didn’t keep that build though. I managed to break it quite early on changing things in VS when I really had no idea what I was doing. I still don’t. Did I mention I’m not that keen on IDE’s? ;-)

>
> Whereas using CMake to generate the VS 2010 files with the 64-bit toolset worked flawlessly, so I used this for testing.

Yes - that was what I did when I replaced the broken build (above); in fact you posted some advice on how to select the correct cmake generator, which is what I’m using with VS now, and os far it seems fine!

Cheers,
--
Ian

[Albrecht Schlosser]

On 29.11.2016 22:42 Ian MacArthur wrote:

>> I can confirm Daniele's experiences. I did the same, and it failed miserably. I installed a patch / update of Visual Studio 2010 because it seemed to lack 64-bit support entirely, but it didn't work after the update. IIRC I got the same issue that "it" told me to update settings by hand, and I gave up as well.
>
> OK; I used the VS 2015 Community version, and once I clicked through the dialogs it spent quite a while doing *something* then I ended up with a solution that appeared to work. Maybe I just got lucky?

Well, this may be the essential difference: I used VS 2010 at that time,
Daniele obviously used VS 2013, and you used VS 2015.

> I didn’t keep that build though. ... Did I mention I’m not that keen on IDE’s? ;-)

Neither am I in the general case, particularly not MS Visual Studio IDE's.

<OT> Although I'm using another IDE mostly for editing, but also for
debugging with a graphical debugger (based on gdb internally). There
_are_ advantages of IDE's. </OT>

>> Whereas using CMake to generate the VS 2010 files with the 64-bit toolset worked flawlessly, so I used this for testing.
>
> Yes - that was what I did when I replaced the broken build (above); in fact you posted some advice on how to select the correct cmake generator, which is what I’m using with VS now, and os far it seems fine!

I'm glad it works for you.