Hi all, my purpose is to share build systems with all possible platforms. the current approcah needs to check for every changes that all build systems are compliant with those changes (new files, new platform dependent changes, ...).
Even if if i am not familiar with native windows programming (and tools to build with VSxxxx), I am not confident that using many build systems is the most flexible (or easiest way) for every one. So if there will be a common build system for all platforms, it will be very helpful for anyone. Can you tell me why MinGW is out of the main stream to build libUV? Why it uses separate makefiles instead of autotools? (only history of libUV, specific consideration, something else). Is it only many efforts to share/mutualise build systems? Regards, Le vendredi 16 décembre 2016 08:58:58 UTC+1, Vincent de RIBOU a écrit : > > Hi all, > > I noticed that many ways are possible to build platform dependent items. > For example, native windows uses Python tool, when MinGW uses custom > makefile and finaly autotools for posix platforms. > > Since I am developping components on many platform types, I think it will > be very interesting to have only one build system, whatever it could be. > > What's your opinion? > Do you thnk it is possible? > > How to validate all configs, complete LibUV solution or subcomponent are > included at the same time in all build systems? > > Many thanks for your comments. > -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
