Re: [Oorexx-devel] Feedback at ooRexx Wiki "How to build", listing of a complete compiler run with warnings (Re: Question ad creating 32-bit ooRexx for Windows
> > the following Windows-related documentation files are currently missing > from the 5.0.0beta directory: > oodguide.pdf oodialog.pdf ooDialog_ReleaseNotes.txt ooRexxTry.pdf > Rony, I don't build oodialog, docs .. you'll have to pick up the 4.2 versions In fact, I'm not even sure how to maintain oodialog: there is oodialog code within the oorexx source tree, and there is a stand-alone oodialog source tree and I don't know if those versions are in sync, and how to (and who will) proceed further. To avoid code duplication, it might be best to remove oodialog from base oorexx, and only maintain it as a stand-alone option. Wouldn't it be nice if we had a standardized interface to getting ooRexx optional packages downloaded and installed? Like "rexx-get" would list available packages compatible with the installed version, and rexx-get oodialog, or rexx-get bsf4oorexx would download (from sourceforge or such) and install them. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Feedback at ooRexx Wiki "How to build", listing of a complete compiler run with warnings (Re: Question ad creating 32-bit ooRexx for Windows
Hi Erich, On 03.05.2017 22:34, Erich Steinböck wrote: > Rony, thanks, I've fixed the "NMake" typo, and the list of required docs. > > CMake defaults to -DCMAKE_BUILD_TYPE=DEBUG. If no CMAKE_BUILD_TYPE is > specified, compiler flag > /Od (no optimization) is used. Hmm, retried it again, and you are right! Must have mixed up the directories while renaming them, sorry for the false alarm! > > all PDF-files made available as a single zip-archive > > I'm refreshing rexxref, rexxpg (and sometimes other) docs after each doc > change .. I really don't > want to have to zip and upload the full bundle each time too. > It should be easy to wget each doc in a loop, if needed. Just use (e. g.) > wget --no-check-certificate > https://sourceforge.net/projects/oorexx/files/oorexx-docs/5.0.0beta/[doc-name].pdf That is an excellent idea, thank you! One thing: the following Windows-related documentation files are currently missing from the 5.0.0beta directory: * oodguide.pdf * oodialog.pdf * ooDialog_ReleaseNotes.txt * ooRexxTry.pdf > > Maybe all warnings are known anyway > > I've already done some work to avoid compiler warnings, but there's still a > lot to do (*). Of > course, we should have clean, warning-free compiles with gcc on Linux and > MSVC on Windows. Yes, it is not easy. ---rony > (*) It's often not straightforward to decide how to go forward. E. g. what > about a warning about > a deprecated function: should I really migrate to the new function with all > necessary research, > coding, and testing, just to avoid a single warning? Should I just suppress > the warning for this > single case? But, then, at some time in the future we might really want to > know about the > deprecation, so why not just keep the warning .. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Feedback at ooRexx Wiki "How to build", listing of a complete compiler run with warnings (Re: Question ad creating 32-bit ooRexx for Windows
Rony, thanks, I've fixed the "NMake" typo, and the list of required docs. CMake defaults to -DCMAKE_BUILD_TYPE=DEBUG. If no CMAKE_BUILD_TYPE is specified, compiler flag /Od (no optimization) is used. all PDF-files made available as a single zip-archive > I'm refreshing rexxref, rexxpg (and sometimes other) docs after each doc change .. I really don't want to have to zip and upload the full bundle each time too. It should be easy to wget each doc in a loop, if needed. Just use (e. g.) wget --no-check-certificate https://sourceforge.net/projects/oorexx/files/oorexx-docs/5.0.0beta/[doc-name].pdf Maybe all warnings are known anyway > I've already done some work to avoid compiler warnings, but there's still a lot to do (*). Of course, we should have clean, warning-free compiles with gcc on Linux and MSVC on Windows. (*) It's often not straightforward to decide how to go forward. E. g. what about a warning about a deprecated function: should I really migrate to the new function with all necessary research, coding, and testing, just to avoid a single warning? Should I just suppress the warning for this single case? But, then, at some time in the future we might really want to know about the deprecation, so why not just keep the warning .. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
