I was really hoping for instructions on what are the arguments that would set the attribute stable=1 on gsl command line.
Maybe the correct question should be how do I tell configure that I want the stable one. Sent from my iPad. Regularly foiled by autocorrect. But duck it.. > On Mar 27, 2016, at 03:37, Pieter Hintjens <[email protected]> wrote: > > Two things here. First, the project itself can have various states. > There are two that interest us: > > * all draft, nothing has been marked stable yet. > * some parts marked as stable (and released), others are draft. > > In the first case zproject should export the whole API (in the project > header file). It didn't do this properly until a few weeks ago, so do > take the latest master. > > In the second case, the project header file exports the stable > classes/methods and then the unstable ones according to what happens > at configure time. > > -Pieter > >> On Fri, Mar 25, 2016 at 4:46 PM, Osiris Pedroso <[email protected]> wrote: >> In case you prefer this format: >> >> G:\malamute>git diff include\mlm_proto.h >> diff --git a/include/mlm_proto.h b/include/mlm_proto.h >> index a6b27e5..1e73a2b 100644 >> --- a/include/mlm_proto.h >> +++ b/include/mlm_proto.h >> @@ -20,9 +20,7 @@ extern "C" { >> // @warning THE FOLLOWING @INTERFACE BLOCK IS AUTO-GENERATED BY ZPROJECT >> // @warning Please edit the model at "api/mlm_proto.api" to make changes. >> // @interface >> -// This is a draft class, and may change without notice. It is disabled in >> -// stable builds by default. If you use this in applications, please ask >> -// for it to be pushed to stable state. Use --enable-drafts to enable. >> +// This API is a draft, and may change without notice. >> #ifdef MLM_BUILD_DRAFT_API >> #define MLM_PROTO_SUCCESS 200 // >> #define MLM_PROTO_FAILED 300 // >> >>> On Fri, Mar 25, 2016 at 10:36 AM Osiris Pedroso <[email protected]> wrote: >>> >>> I have made some changes to zproject (Windows building scripts) and >>> regenerated zeromq/malamute project with those changes using these steps: >>> >>> #!/usr/bin/env bash >>> >>> set -x >>> >>> ( cd ~/git/zproject && ./autogen.sh && ./configure && make && sudo make >>> install ) || exit 1 >>> >>> #git clone --depth 1 https://github.com/imatix/gsl gsl >>> ( cd ~/git/gsl/src && make -j4 && sudo make install ) || exit 1 >>> >>> #git clone --depth 1 https://github.com/zeromq/czmq czmq >>> ( cd ~/git/czmq && gsl -target:* project.xml ) || exit 1 >>> >>> #git clone --depth 1 https://github.com/zeromq/malamute malamute >>> ( cd ~/git/malamute && gsl -target:* project.xml ) || exit 1 >>> >>> The problem is that I end up with differences between the generated files >>> which are note related to my changes to GSL files >>> (malamute/include/mlm_proto.h): >>> >>> OLD: >>> >>> // This is a draft class, and may change without notice. It is disabled >>> in >>> // stable builds by default. If you use this in applications, please ask >>> // for it to be pushed to stable state. Use --enable-drafts to enable. >>> >>> NEW: >>> >>> // This API is a draft, and may change without notice. >>> >>> From the .GSL script, it seems to indicate that one was built with >>> project.stable set and the other was not. >>> >>> How do I specify to gsl command line that I want to build with stable set? >> >> >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
