@Mark - are you using VS2008 on windows 10? I’m trying to piece together the build environment from this line:
https://github.com/apache/commons-daemon/blob/master/src/native/windows/README.txt#L31-L32 refrencing Mladen Turk's repo https://github.com/mturk/cmsc/tree/cb6be932c8c95a46262a64a89e68aae620dfdcee <https://github.com/mturk/cmsc/tree/cb6be932c8c95a46262a64a89e68aae620dfdcee> suggesting using Visual Studio 2008 with "cl is 15.00.21022.08,” which I can’t find a windows 10 installer for. That said, you have the documentation for buildling the tomcat binaries https://cwiki.apache.org/confluence/display/TOMCAT/Common+Native+Build+Environment <https://cwiki.apache.org/confluence/display/TOMCAT/Common+Native+Build+Environment> which again references Turk’s repo with a later commit “132baba36” and using Windows 10, but Turk still says to use Visual Studio 2008. If I install the latest windows visual studio installation and run the nmake I do get files generated out of the “nmake” commands, but I’m still consistently unable to run Turk’s “setenv.bat /x86”. Personally I want to understand what’s going on here, but this is definitely a build environmen that is quite foreign to me. I don’t want to hold up the release of Daemon 1.2.4 with my lack of aptitude in the “C” build departments. Thoughts? -Rob > On Nov 19, 2020, at 11:00 AM, Rob Tompkins <chtom...@gmail.com> wrote: > > I’m going to have to say that building and releasing daemon isn’t very clear > to me as to how to proceed. The documentation that we do have namely: > https://github.com/apache/commons-daemon/blob/master/HOWTO-RELEASE.txt > <https://github.com/apache/commons-daemon/blob/master/HOWTO-RELEASE.txt>, and > https://github.com/apache/commons-daemon/blob/master/src/native/windows/README.txt > > <https://github.com/apache/commons-daemon/blob/master/src/native/windows/README.txt> > aren’t enough help for me to get the C portion of the project to build in > windows appropriately. > > @Mark - I’m happy to validate the RC, but given my problems building the > project generally, I don’t know my +1 is actually of any service because > there’s far more here than I originally thought. > > All that said, I will continue to play around with the linux build for the > time being as to understand it more. But, I don’t think that you guys should > wait for me to do the build for this 1.2.4 release because I’m going to be > too slow. > > Cheers, > -Rob > >> On Nov 17, 2020, at 10:23 AM, Rob Tompkins <chtom...@gmail.com >> <mailto:chtom...@gmail.com>> wrote: >> >> >> >>> On Nov 16, 2020, at 7:35 AM, Rob Tompkins <chtom...@gmail.com >>> <mailto:chtom...@gmail.com>> wrote: >>> >>> >>> >>>> On Nov 16, 2020, at 2:53 AM, Mark Thomas <ma...@apache.org >>>> <mailto:ma...@apache.org>> wrote: >>>> >>>> On 15/11/2020 22:36, Rob Tompkins wrote: >>>>> So this is my first time in here. You build both unix and windows >>>>> binaries? Do you normally do this using windows linux subsystem as a >>>>> mechanism to get both sets of binaries from a single machine or do you >>>>> perform two builds? >>>> >>>> I do the majority of the release from a Linux box, following the steps >>>> in /HOWTO-RELEASE.txt. >>>> >>>> I build the the Windows binaries on a Windows VM and transfer the files. >>>> >>>> We don't provide binaries for any other platform. >>>> >>>> The unix source does require buildconf to be run which is why I do the >>>> majority of the release on Linux. >>> >>> I see. Thanks. Will try to get it built today. >> >> Just an update….still finding around with the windows build in-between my >> day-job activities. >> >> Cheers, >> -Rob >> >>> >>> -Rob >>> >>>> >>>> Mark >>>> >>>> >>>>> >>>>> -Rob >>>>> >>>>>>> On Nov 14, 2020, at 3:53 PM, Rob Tompkins <chtom...@gmail.com >>>>>>> <mailto:chtom...@gmail.com>> wrote: >>>>>> >>>>>> >>>>>> >>>>>>> On Nov 14, 2020, at 1:01 PM, Mark Thomas <ma...@apache.org >>>>>>> <mailto:ma...@apache.org>> wrote: >>>>>>> >>>>>>> On 13/11/2020 19:19, Rob Tompkins wrote: >>>>>>>> Hm….don’t have a windows machine laying around. Could maybe use AWS to >>>>>>>> stand up something like that for the release. >>>>>>> >>>>>>> I can build and sign the Windows binaries for you once you have a tag. >>>>>>> >>>>>> >>>>>> Will work on this tomorrow >>>>>> >>>>>> -Rob >>>>>> >>>>>>> Mark >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> -Rob >>>>>>>> >>>>>>>>>> On Nov 13, 2020, at 2:15 PM, Gary Gregory <garydgreg...@gmail.com >>>>>>>>>> <mailto:garydgreg...@gmail.com>> wrote: >>>>>>>>> >>>>>>>>> Hi Rob, >>>>>>>>> >>>>>>>>> Thanks for the help. >>>>>>>>> Do you have access to a Windows PC or VM? >>>>>>>>> >>>>>>>>> Gary >>>>>>>>> >>>>>>>>>> On Fri, Nov 13, 2020, 13:28 Rob Tompkins <chtom...@gmail.com >>>>>>>>>> <mailto:chtom...@gmail.com>> wrote: >>>>>>>>> >>>>>>>>>> If I recall correctly, I offered to do the next release when the >>>>>>>>>> time came >>>>>>>>>> in order to set up the release plugin. @MarkT - let me know what >>>>>>>>>> you’re >>>>>>>>>> thinking. >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> -Rob >>>>>>>>>> >>>>>>>>>>> On Nov 13, 2020, at 1:14 PM, Gary Gregory <garydgreg...@gmail.com >>>>>>>>>>> <mailto:garydgreg...@gmail.com>> >>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> Hi all & markt, >>>>>>>>>>> >>>>>>>>>>> Any thoughts on getting the recent fixes out in a release sooner >>>>>>>>>>> rather >>>>>>>>>>> than later? >>>>>>>>>>> >>>>>>>>>>> Gary >>>>>>>>>> >>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>>>>>>>> <mailto:dev-unsubscr...@commons.apache.org> >>>>>>>>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>>>>>>>> <mailto:dev-h...@commons.apache.org> >>>>>>>>>> >>>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>>>>>> <mailto:dev-unsubscr...@commons.apache.org> >>>>>>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>>>>>> <mailto:dev-h...@commons.apache.org> >>>>>>>> >>>>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>>> <mailto:dev-unsubscr...@commons.apache.org> >>>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>>> <mailto:dev-h...@commons.apache.org> >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>> <mailto:dev-unsubscr...@commons.apache.org> >>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>> <mailto:dev-h...@commons.apache.org>
