I revoke this “master.c” idea. It makes incremental compiling ridiculously 
slow. It might work for production builds, but definitely not for development.


Best regards,



From: Simon Rozman [mailto:si...@rozman.si] 
Sent: Thursday, November 7, 2019 2:06 PM
To: 'Lev Stipakov' <lstipa...@gmail.com>; 'Gert Doering' <g...@greenie.muc.de>
Cc: 'Antonio Quartulli' <a...@unstable.cc>; 'openvpn-devel' 
Subject: Re: [Openvpn-devel] [PATCH applied] Re: VLAN: add basic VLAN tagging 


We could introduce a master.c file which would include:


#include "argv.c"

#include "auth_token.c"

#include "base64.c"

#include "block_dns.c"

#include "buffer.c"




#include "status.c"

#include "tls_crypt.c"

#include "tun.c"

#include "win32.c"


And then have Makefile.ac and MSVC project files compile the master.c only.


Best regards,




Besides this, we need to fix this whole MSVC mess - all other platforms
are just done with "add new source file to the Makefile.ac" and done
(including mingw builds), and then MSVC is broken again, and this will
happen again and again.   

Is there no reasonable way to build these project files from Makefile.ac?


I see no reasonable way. Selva, Simon - opinions?


We could probably have a templatized project file and script which inserts 
source files to there

based on content of Makefile.ac, but I don't like it. I consider necessity of 
modifying VS project

a lesser evil. 


(you open it and it just works)



Attachment: smime.p7s
Description: S/MIME cryptographic signature

Openvpn-devel mailing list

Reply via email to