RE: [fltk.general] fltk package install on windows blazing new trails (not in good way) in root install directory [General Use]

[MacArthur, Ian (Leonardo, UK)]

> On Windows any thoughts on why FLTK puts its package
> stuff in install/CMake and not lib/cmake/fltk-1.3.4


Cmake is still a relatively new thing for us, historically our builds have always been autoconf based, so to some extent we are still "finding our way" with this.

If there's "established best practices", then I imagine we'd be keen to follow the pattern.

If you have suggestions, patches, guidance in general, we'd welcome your contributions; we are trying to make the Cmake support play well with the wider ecosystem, and input from experienced users of Cmake is valuable.

If you have any suggestions for patches etc., can you post them in the STR system please, so we can get back to them, and also any discussions can go here or over in fltkcoredev...

Cheers,



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.
********************************************************************

[Brian Davis]

On Friday, March 24, 2017 at 4:30:28 AM UTC-5, MacArthur, Ian (Leonardo, UK) wrote:

> On Windows any thoughts on why FLTK puts its package
> stuff in install/CMake and not lib/cmake/fltk-1.3.4


Cmake is still a relatively new thing for us, historically our builds have always been autoconf based, so to some extent we are still "finding our way" with this.

If there's "established best practices", then I imagine we'd be keen to follow the pattern.

If you have suggestions, patches, guidance in general, we'd welcome your contributions; we are trying to make the Cmake support play well with the wider ecosystem, and input from experienced users of Cmake is valuable.

If you have any suggestions for patches etc., can you post them in the STR system please, so we can get back to them, and also any discussions can go here or over in fltkcoredev...

I posted my recommendations on git hub on the fltk/test

https://github.com/fltk/test-only/pulls
https://github.com/fltk/test-only/pull/2/files

[Greg Ercolano]

On 03/29/17 19:14, Brian Davis wrote:
> On Friday, March 24, 2017 at 4:30:28 AM UTC-5, MacArthur, Ian (Leonardo, UK) wrote:
> If you have suggestions, patches, guidance in general, we'd welcome your contributions;
> we are trying to make the Cmake support play well with the wider ecosystem, and input
> from experienced users of Cmake is valuable.
>
> If you have any suggestions for patches etc., can you post them in the STR system
> please, so we can get back to them, and also any discussions can go here or over in fltkcoredev...
>
> I posted my recommendations on git hub on the fltk/test
>
> https://github.com/fltk/test-only/pulls
> https://github.com/fltk/test-only/pull/2/files

Ah, the clarity of github's UI. Bless them.

Thing is, until we officially switch to git (and perhaps github),
we should probably stick to STR's for now, so we can have a good
record of mods, as anything posted to 'test-only' will likely be lost
at some point.