Hi Marcus,

Am 15.05.21 um 08:57 schrieb Marcus:
> Am 14.05.21 um 21:56 schrieb Arrigo Marchiori:
>> I would go for option A- because option B- would lead to _very_ long
>> command lines and I would expect problems.
>>
>> But would I stomp on anyone's feet if I did that? Would it be bad
>> practice? Would it violate any standards?
>>
>> I am open to suggestions and criticism. Please let me hear your
>> opinion!
>
> I'm not a core developer, so I don't know the details. However,
> renaming such essential keywords like "INCLUDE" and "LIB" is indeed a
> heavy change.
>
> IMHO it's the same like switching the build system to gmake, scons or
> whatever. It has to be done very carefully and would be an enormous
> obstacle for us. There are f...cking many makefiles that need to be
> changed. We have tried to change the build system more than one time
> and both were not done until the end.
>
> So, now we have a mix of 3-4 build systems inside the code. With a mix
> of renamed keywords it won't get easier to maintain the code and even
> not for new vontuneers to understand this.
>
> What is currently used for building on Windows?
MSVC 2008 (EOL since 2018). The file isn't downloadable anymore from
Microsoft.
> Any (good) need to chnge thisto VS 2015?

We need to move to a new compiler at some point, MSVC would be supported
until 2025.

Regards,

   Matthias

>
> Who should do this change and is there a guarantee that the person is
> doing it until the end?
>
> Is it for sure that this is only influencing how we can build on
> Windows or has it any side effects on the other platforms? If so,
> renaming is more than a normal obstacle.
>
> We need to discuss and decide this very detailed and carefully.
>
> Sorry for these strong words and questions. However, my gut feeling
> says "this is not a good idea".
>
> My 2 ct.
>
> Marcus
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to