Den tors 12 aug. 2021 kl 04:00 skrev Justin Erenkrantz < jus...@erenkrantz.com>:
> Thanks for the patch. > > Is the release|debug_<arch> a standard CMake output directory or specific > to how TortoiseSVN is building Serf? > TortoiseSVN is building Serf using NAnt [1] with a (AFAIK) handtuned build configuration. So I assume it is specific to the way TortoiseSVN is building Serf. Kind regards, Daniel [1] http://nant.sourceforge.net/ Cheers. — justin > > On Wed, Jul 21, 2021 at 8:36 AM Daniel Sahlberg < > daniel.l.sahlb...@gmail.com> wrote: > >> Hi, >> >> TortoiseSVN is importing SERF via a svn:externals definition: >> [[[ >> https://svn.apache.org/repos/asf/serf/tags/1.3.9 serf >> ]]] >> >> The build system creates a few new directories within the serf directory >> for temporary build files. These clutter svn status and makes it more >> difficult to see if there are any real changes. >> >> I would propose to add a few more folders in svn:ignore. (I have already >> done similar modifications in the Subversion repository, see r1891003). >> >> [[[ >> Index: serf >> =================================================================== >> --- serf (revision 1891700) >> +++ serf (working copy) >> >> Property changes on: serf >> ___________________________________________________________________ >> Modified: svn:ignore >> ## -1,7 +1,15 ## >> *.os >> .gdb_history >> Debug >> +debug_win32 >> +debug_win32_static >> +debug_x64 >> +debug_x64_static >> Release >> +release_win32 >> +release_win32_static >> +release_x64 >> +release_x64_static >> .sconsign.dblite >> .sconf_temp >> config.log >> ]]] >> >> An alternative approach would be to ignore debug_* and release_*, this >> might help in case there is a future architecture (eg arm). >> >> (I realise this will be made on /trunk and not affect the tag that >> TortoiseSVN is pulling in until there is a new release, but it will be >> better in the future). >> >> Kind regards, >> Daniel Sahlberg >> >
