Yeah sure. Let's go to something more productive. ;-) On 13.4.2016 23:14, Pieter Hintjens wrote: > I assume you hacked project.xml to make that work since it starts by > including 'license.xml'. > > I assume also this is a learning thing for you and you're not actually > solving any specific problems. In that case, enjoy. I'll leave this > thread for now. > > On Wed, Apr 13, 2016 at 10:59 PM, Matjaž Ostroveršnik > <[email protected]> wrote: >> >> On 13.4.2016 22:37, Pieter Hintjens wrote: >>> gsl project.xml will not work from any folder; it will scatter >>> generated files all over the place. >>> >>> usage rule is you build the model, in its directory. Never use a path >>> to a model (xml) file that you pass to gsl. >> If this is the intention, then we have a bug. ;-) >> >> [ostri@uran ~/zstuff/build/tmp]$ gsl ../top/project.xml >> GSL/4.1c Copyright (c) 1996-2016 iMatix Corporation >> gsl/4 I: Processing ../top/project.xml... >> gsl/4 M: Generating skeleton for src/malamute.c >> gsl/4 M: Generating skeleton for src/mshell.c >> gsl/4 M: Generating skeleton for src/mlm_tutorial.c >> gsl/4 M: Generating skeleton for src/mlm_tutorial_curve.c >> gsl/4 M: Generating skeleton for src/mlm_perftest.c >> gsl/4 M: Generating skeleton for src/mlm_selftest.c >> gsl/4 M: Generating skeleton for include/malamute.h >> gsl/4 M: Generating skeleton for include/mlm_proto.h >> gsl/4 M: Generating skeleton for src/mlm_proto.c >> gsl/4 M: Generating skeleton for include/mlm_server.h >> gsl/4 M: Generating skeleton for src/mlm_server.c >> gsl/4 M: Generating skeleton for include/mlm_client.h >> gsl/4 M: Generating skeleton for src/mlm_client.c >> gsl/4 M: Generating skeleton for src/mlm_msg.h >> gsl/4 M: Generating skeleton for src/mlm_msg.c >> gsl/4 M: Generating skeleton for src/mlm_stream_simple.h >> gsl/4 M: Generating skeleton for src/mlm_stream_simple.c >> gsl/4 M: Generating skeleton for src/mlm_mailbox_simple.h >> gsl/4 M: Generating skeleton for src/mlm_mailbox_simple.c >> gsl/4 M: Generating initial .gitignore file >> gsl/4 M: Generating initial .gitattributes file >> gsl/4 M: Building Java JNI binding (java) >> gsl/4 M: Building Python binding (python) >> gsl/4 M: Building Ruby binding (ruby) >> gsl/4 M: Building Travis CI scripts (travis) >> gsl/4 M: Generating skeleton .travis.yml script >> gsl/4 M: Building packaging for Docker (docker) >> gsl/4 M: Building Microsoft Visual Studio 2015 (vs2015) >> gsl/4 M: Building GYP build system (project.gyp) (gyp) >> gsl/4 M: E: please checkout libzmq into ../libzmq >> gsl/4 M: E: please checkout czmq into ../czmq >> gsl/4 M: Building GNU build system (autotools) >> gsl/4 M: Building CMake build system (cmake) >> >> >>> On Wed, Apr 13, 2016 at 10:12 PM, Matjaž Ostroveršnik >>> <[email protected]> wrote: >>>> It is not that by intention that want to work around the design. >>>> There are just few inconsistency I've encountered. Perhaps my knowledge >>>> not deep enough. >>>> >>>> gsl project.xml - it works from any folder (e.g. gsl >>>> ~/zstuff/malamute/project.xml) >>>> gsl mlm_proto.xml - it works fine from src folder, but it fails from >>>> different folder >>>> >>>> The same program, but two different behaviors. What is the usage rule >>>> for gsl? >>>> >>>> On 13.4.2016 21:59, Pieter Hintjens wrote: >>>>> Why are you trying to work around the design? If you could be explicit >>>>> about that it would really help. I mean, if you try to use a knife as >>>>> a screwdriver and the tip breaks off, it's not the knife's fault. Can >>>>> you explain why you are trying to run gsl in the *wrong place* and why >>>>> it's "unfortunate" that does not work? >>>>> >>>>> >>>>> On Wed, Apr 13, 2016 at 9:44 PM, Matjaž Ostroveršnik >>>>> <[email protected]> wrote: >>>>>> I am (unfortunatelly ;-) ) confirming. >>>>>> Found this in src/Makemodule.am >>>>>> >>>>>> # Produce generated code from models in the src directory >>>>>> code: >>>>>> cd $(srcdir)/src; gsl -topdir:.. -zproject:1 -q mlm_proto.xml >>>>>> cd $(srcdir)/src; gsl -topdir:.. -zproject:1 -q >>>>>> mlm_client.xml >>>>>> cd $(srcdir)/src; gsl -topdir:.. -zproject:1 -q >>>>>> mlm_server.xml >>>>>> gsl -target:- project.xml >>>>>> >>>>>> >>>>>> On 13.4.2016 21:40, Pieter Hintjens wrote: >>>>>>> No hypothesis. I'm telling you a fact. If you run gsl in the wrong >>>>>>> place *it will not work*. Please do not debug misuse. >>>>>>> >>>>>>> On Wed, Apr 13, 2016 at 8:57 PM, Matjaž Ostroveršnik >>>>>>> <[email protected]> wrote: >>>>>>>> Pieter hypothesis is that the src folder is hard coded. ;-) >>>>>>>> >>>>>>>> >>>>>>>> On 13.4.2016 20:10, Kevin Sapper wrote: >>>>>>>> >>>>>>>> Now you got me curious :) >>>>>>>> >>>>>>>> The error message with commented license.xml should be: >>>>>>>> $ gsl src/mlm_proto.xml >>>>>>>> 2016/04/13 20:04:48: GSL/4.1a/github Copyright (c) 1996-2011 iMatix >>>>>>>> Corporation >>>>>>>> 2016/04/13 20:04:48: gsl/4 I: Processing src/mlm_proto.xml... >>>>>>>> 2016/04/13 20:04:48: (zproto_codec_c.gsl 206) Can't open output file: >>>>>>>> ../include/mlm_proto.h >>>>>>>> >>>>>>>> Which again happens because the current working directory is applied >>>>>>>> to all >>>>>>>> relative paths. >>>>>>>> >>>>>>>> >>>>>>>> On Mi, Apr 13, 2016 at 7:58 , Matjaž Ostroveršnik >>>>>>>> <[email protected]> wrote: >>>>>>>> >>>>>>>> I commented out the license file, but the same. >>>>>>>> >>>>>>>> I am getting >>>>>>>> GSL/4.1c Copyright (c) 1996-2016 iMatix Corporation >>>>>>>> gsl/4 I: Processing src/mlm_proto.xml... >>>>>>>> (zproto_lib.gsl 99) Undefined expression: class.load_file (...) >>>>>>>> >>>>>>>> >>>>>>>> On 13.4.2016 19:50, Kevin Sapper wrote: >>>>>>>> >>>>>>>> OK, I just thought a little bit harder ;) >>>>>>>> >>>>>>>> src/mlm_proto.xml includes a second xml files: <include filename = >>>>>>>> "license.xml" />. Where filename is a relative path from the current >>>>>>>> working >>>>>>>> directory. Thus if you execute gsl from project root directory it is >>>>>>>> not >>>>>>>> able to find the src/license.xml. >>>>>>>> >>>>>>>> But from project root you can run make code. >>>>>>>> >>>>>>>> On Mi, Apr 13, 2016 at 7:44 , Matjaž Ostroveršnik >>>>>>>> <[email protected]> wrote: >>>>>>>> >>>>>>>> Hi Kevin, >>>>>>>> >>>>>>>> Thanks for fast reply. I believe it is not problem with tabs. >>>>>>>> The same command in src folder succeeds, while one folder above, but >>>>>>>> with >>>>>>>> proper reference to the xml file it fails. >>>>>>>> My assumption is that gsl takes "instructions" from some default place, >>>>>>>> unless it is explicitly stated. And I do not know this place.;-) >>>>>>>> >>>>>>>> Best regards >>>>>>>> >>>>>>>> Matjaž >>>>>>>> >>>>>>>> On 13.4.2016 19:36, Kevin Sapper wrote: >>>>>>>> >>>>>>>> Hi Matjaž, >>>>>>>> >>>>>>>> without being able to take a closer look now, GSL does not like tabs >>>>>>>> at the >>>>>>>> beginning of the line. >>>>>>>> >>>>>>>> Am 13.04.2016 6:16 nachm. schrieb "Matjaž Ostroveršnik" >>>>>>>> <[email protected]>: >>>>>>>>> Hi veterans, >>>>>>>>> >>>>>>>>> I am trying to understand how gsl woks. Yes I read the instructions >>>>>>>>> (https://github.com/imatix/gsl) >>>>>>>>> >>>>>>>>> command >>>>>>>>> gsl mlm_proto.xml >>>>>>>>> >>>>>>>>> executed from malamute/src folder >>>>>>>>> properly generates mlm_proto.c and mlm_proto.bnf in the current >>>>>>>>> directory >>>>>>>>> >>>>>>>>> command >>>>>>>>> gsl src/mlm_proto.xml >>>>>>>>> >>>>>>>>> executed from one folder above produces >>>>>>>>> >>>>>>>>> GSL/4.1c Copyright (c) 1996-2016 iMatix Corporation >>>>>>>>> gsl/4 I: Processing src/mlm_proto.xml... >>>>>>>>> (zproto_lib.gsl 99) Undefined expression: class.load_file (...) >>>>>>>>> >>>>>>>>> obviously gsl gets some additional input from files in current >>>>>>>>> directory. >>>>>>>>> 1. Which files are those? >>>>>>>>> 2. Can I explicitly state where to take this file from? >>>>>>>>> 3. What the following command is supposed to do? (explanation of >>>>>>>>> parameters) >>>>>>>>> gsl -topdir:.. -zproject:1 -q mlm_proto.xml >>>>>>>>> >>>>>>>>> >>>>>>>>> Thanks in advance >>>>>>>>> >>>>>>>>> Matjaž >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>> _______________________________________________ >>>>>> 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 >>> _______________________________________________ >>> 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
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
