Re: [sigrok-devel] Where/how to contribute an exporter
Hello Marc, It's unfortunate that you apparently feel that the help that was given was unhelpful. While I wasn't involved in the discussion at hand, I'd like to point out that we do welcome all contributors and generally try to help them as much as time permits. We don't ever want you to feel like you can't ask questions, so your response is a little concerning for me. I would like to know whether you have any suggestions for us on how we can avoid this situation in the future. If you don't want to share this publicly for one reason or another, you can also mail me directly. All the best, -Soeren On Sat, 2019-12-21 at 15:57 +, Marc Jacobi wrote: > Yeah I stopped. > I was not enjoying the "type of help" I received and was not looking > forward to asking more questions - so I went to do something > different. > Do with the code what you will... > Marc > From: Gerhard Sittig > Sent: Saturday, December 21, 2019 2:21 PM > To: sigrok-devel@lists.sourceforge.net < > sigrok-devel@lists.sourceforge.net> > Subject: Re: [sigrok-devel] Where/how to contribute an exporter > > On Thu, 2019-09-26 at 05:28 +, Marc Jacobi wrote: > > > > Thanks for the pointers. Looks like 'output' is the right place. > > > > I though that interfacing with this would be handy: > > https://wavedrom.com/ > > > > Basically a JSON format. > > Hi Marc! > > Got silent here and in your github repo. > > https://github.com/obiwanjacobi/libsigrok > > The mailing list is good for putting something "on record", or > looking up stuff after months or years have passed. If you are > looking for higher interaction or deeper discussions on > development, IRC could be a better fit. > > Hope you overcame past obstacles, and can continue development? > It's apparent that you have an interest in getting this format > supported by the project, and further improve existing support. :) > > > I have massaged the version that you came up with, to reduce the > remaining amount of work for the maintainer to accept it into the > mainline code base. The resulting version is here: > > > https://repo.or.cz/libsigrok/gsi.git/shortlog/refs/heads/wavedrom-output-v2 > git://repo.or.cz/libsigrok/gsi.git wavedrom-output-v2 > > This should work as well as your implementation did, just fit > into the project's style a little better. You were almost there. > Just an issue of rather high a memory consumption remains, which > can get addressed later. > > I have also started a wiki page for the wavedrom file format. As > of now it's rather stupid and mostly empty. You may want to fill > in some more useful information, see the other file format pages > for ideas what to put there. You find the other pages by starting > at the file formats page. > > https://sigrok.org/wiki/Input_output_formats > https://sigrok.org/wiki/File_format:Wavedrom > > > Thank you for starting the output file format support, and I hope > you keep contributing to the project. > > > virtually yours > Gerhard Sittig > -- > If you don't understand or are scared by any of the above > ask your parents or an adult to help you. > > > ___ > sigrok-devel mailing list > sigrok-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sigrok-devel > ___ > sigrok-devel mailing list > sigrok-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sigrok-devel ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
On Sat, 2019-12-21 at 14:21 +0100, Gerhard Sittig wrote: > > I have massaged the version that you came up with, to reduce the > remaining amount of work for the maintainer to accept it into the > mainline code base. The resulting version is here: > > https://repo.or.cz/libsigrok/gsi.git/shortlog/refs/heads/wavedrom-output-v2 > git://repo.or.cz/libsigrok/gsi.git wavedrom-output-v2 Good news everyone! Your output module and the additional adjustment got accepted, and will be part of tomorrow's downloads after the nightly build pick up that implementation. Enjoy! virtually yours Gerhard Sittig -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
Yeah I stopped. I was not enjoying the "type of help" I received and was not looking forward to asking more questions - so I went to do something different. Do with the code what you will... Marc From: Gerhard Sittig Sent: Saturday, December 21, 2019 2:21 PM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter On Thu, 2019-09-26 at 05:28 +, Marc Jacobi wrote: > > Thanks for the pointers. Looks like 'output' is the right place. > > I though that interfacing with this would be handy: > https://wavedrom.com/ > > Basically a JSON format. Hi Marc! Got silent here and in your github repo. https://github.com/obiwanjacobi/libsigrok The mailing list is good for putting something "on record", or looking up stuff after months or years have passed. If you are looking for higher interaction or deeper discussions on development, IRC could be a better fit. Hope you overcame past obstacles, and can continue development? It's apparent that you have an interest in getting this format supported by the project, and further improve existing support. :) I have massaged the version that you came up with, to reduce the remaining amount of work for the maintainer to accept it into the mainline code base. The resulting version is here: https://repo.or.cz/libsigrok/gsi.git/shortlog/refs/heads/wavedrom-output-v2 git://repo.or.cz/libsigrok/gsi.git wavedrom-output-v2 This should work as well as your implementation did, just fit into the project's style a little better. You were almost there. Just an issue of rather high a memory consumption remains, which can get addressed later. I have also started a wiki page for the wavedrom file format. As of now it's rather stupid and mostly empty. You may want to fill in some more useful information, see the other file format pages for ideas what to put there. You find the other pages by starting at the file formats page. https://sigrok.org/wiki/Input_output_formats https://sigrok.org/wiki/File_format:Wavedrom Thank you for starting the output file format support, and I hope you keep contributing to the project. virtually yours Gerhard Sittig -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
On Thu, 2019-09-26 at 05:28 +, Marc Jacobi wrote: > > Thanks for the pointers. Looks like 'output' is the right place. > > I though that interfacing with this would be handy: > https://wavedrom.com/ > > Basically a JSON format. Hi Marc! Got silent here and in your github repo. https://github.com/obiwanjacobi/libsigrok The mailing list is good for putting something "on record", or looking up stuff after months or years have passed. If you are looking for higher interaction or deeper discussions on development, IRC could be a better fit. Hope you overcame past obstacles, and can continue development? It's apparent that you have an interest in getting this format supported by the project, and further improve existing support. :) I have massaged the version that you came up with, to reduce the remaining amount of work for the maintainer to accept it into the mainline code base. The resulting version is here: https://repo.or.cz/libsigrok/gsi.git/shortlog/refs/heads/wavedrom-output-v2 git://repo.or.cz/libsigrok/gsi.git wavedrom-output-v2 This should work as well as your implementation did, just fit into the project's style a little better. You were almost there. Just an issue of rather high a memory consumption remains, which can get addressed later. I have also started a wiki page for the wavedrom file format. As of now it's rather stupid and mostly empty. You may want to fill in some more useful information, see the other file format pages for ideas what to put there. You find the other pages by starting at the file formats page. https://sigrok.org/wiki/Input_output_formats https://sigrok.org/wiki/File_format:Wavedrom Thank you for starting the output file format support, and I hope you keep contributing to the project. virtually yours Gerhard Sittig -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
Installed 'libpython3.6-dev' - thanks Jorg - and that got me all the way. I did run into some other issues (not able to find the shared object files) but I could find the answers online. I have just fixed some last issues and the wavedrom exported now exports a valid wavedrom json file. Note however, that wavedrom (itself) does not work well with very large data sets - it takes very very long. So long I didn't wait for it. I have tested the wavedrom exporter with a downloaded (Z80 - yeah! ) dump and this command line: sigrok-cli --input-format srzip --input-file z80_kc85_kc85-cpuclk.sr --output-format wavedrom --output-file z80_kc85_kc85-cpuclk.json So please do a code review and see if this can be merged into master. https://github.com/obiwanjacobi/libsigrok/blob/master/src/output/wavedrom.c (note - I did also change other files) In the meantime I will try out some other dumps and compare them against PulseView. Marc From: Jörg Sent: Wednesday, October 9, 2019 9:39 AM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter Am Wed, 9 Oct 2019 17:31:02 +1000 schrieb Stuart Longland : > On 9/10/19 5:06 pm, Marc Jacobi wrote: > > > > So I set out to build the libsigrokdecode and sigrok-cli projects. > > However, when building the decode library I get an error in the > > 'configure' step: > > "Cannot find Python 3 development headers." > > I did install python3.6 (sudo apt-get install python3.6). > > > > Q => How do I get these development headers? > > Usually if you're running a Debian derivative (Ubuntu is) the package > you want is `python3-dev` (or possibly `libpython3-dev`). or libpython3.6-dev I use Synaptic: search 'python' and install the part 'libpyth*-dev' from your python-version. ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
On 9/10/19 5:06 pm, Marc Jacobi wrote: So I set out to build the libsigrokdecode and sigrok-cli projects. However, when building the decode library I get an error in the 'configure' step: "Cannot find Python 3 development headers." I did install python3.6 (sudo apt-get install python3.6). Q => How do I get these development headers? Usually if you're running a Debian derivative (Ubuntu is) the package you want is `python3-dev` (or possibly `libpython3-dev`). -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere. ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
Ok, 'make install' worked. After some searching around, I figured I could perhaps try the cli to test 'our' new exporter. Q => Is this a correct assumption? I saw command line options for loading a file and an output-format - does that cover exporters? So I set out to build the libsigrokdecode and sigrok-cli projects. However, when building the decode library I get an error in the 'configure' step: "Cannot find Python 3 development headers." I did install python3.6 (sudo apt-get install python3.6). Q => How do I get these development headers? From: Marc Jacobi Sent: Tuesday, October 8, 2019 9:33 AM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter As I said before: * Yes, I am a linux noob * Yes, I am on Windows running the Linux subsystem. * No, I am not building on Windows, but Ubuntu16 (subsystem) What I understand of the build process is, that in order to build the PusleView monolith I have to install a gazillion things. Perhaps I was hoping there was a debug build (pre-made) somewhere that would allow you to just overwrite the module/library you're working on. Or is there a integration/unit test harness somewhere? Anyway, some pointers would be appreciated - what to read, what to install/what not to install. I will try 'make install' (without having a clue what to do with it...) I have shared my repo in github I have cloned and updated, so if anyone wants to try to build and run the exporter, I would be interested to hear the results. But as a development cycle, this sounds horrible. From: Geert Stappers Sent: Monday, October 7, 2019 11:22 PM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter On Mon, Oct 07, 2019 at 06:25:42PM +0200, Geert Stappers wrote: > On Fri, Oct 04, 2019 at 08:50:26AM +, Marc Jacobi wrote: > > Can anyone please help me test my code? > > :-)aim for *our* code > > > > Sent: Monday, September 30, 2019 7:45 PM > > > > Okay, I have made a draft of my code - purely based on the compiler. > > > > Now I like to run it. Should I do 'make install' or is there another > > way of testing out my exporter output logic. > > > > Looking at my install of PulseView I don't see any dlls so every > > library is statically linked...? That would mean I need to pull in > > all the source code and build the UI..? > > > When I saw the "make install", I did think "yes". > > When I saw "I don't see any DLLs", I did think "Oops, Microsoft Windows". > > > > Original Poster can do serveral things: > * Try to understand the build process of sigrok on Microsoft Windows. > * Share the wavedrom code to allow others build attemps (any platform) > on the new wavedrom code. > https://github.com/obiwanjacobi/libsigrok/blob/master/src/output/wavedrom.c And I might be wrong on that O.P. is developing on MSFT Windows. Cheers Geert Stappers ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
As I said before: * Yes, I am a linux noob * Yes, I am on Windows running the Linux subsystem. * No, I am not building on Windows, but Ubuntu16 (subsystem) What I understand of the build process is, that in order to build the PusleView monolith I have to install a gazillion things. Perhaps I was hoping there was a debug build (pre-made) somewhere that would allow you to just overwrite the module/library you're working on. Or is there a integration/unit test harness somewhere? Anyway, some pointers would be appreciated - what to read, what to install/what not to install. I will try 'make install' (without having a clue what to do with it...) I have shared my repo in github I have cloned and updated, so if anyone wants to try to build and run the exporter, I would be interested to hear the results. But as a development cycle, this sounds horrible. From: Geert Stappers Sent: Monday, October 7, 2019 11:22 PM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter On Mon, Oct 07, 2019 at 06:25:42PM +0200, Geert Stappers wrote: > On Fri, Oct 04, 2019 at 08:50:26AM +, Marc Jacobi wrote: > > Can anyone please help me test my code? > > :-)aim for *our* code > > > > Sent: Monday, September 30, 2019 7:45 PM > > > > Okay, I have made a draft of my code - purely based on the compiler. > > > > Now I like to run it. Should I do 'make install' or is there another > > way of testing out my exporter output logic. > > > > Looking at my install of PulseView I don't see any dlls so every > > library is statically linked...? That would mean I need to pull in > > all the source code and build the UI..? > > > When I saw the "make install", I did think "yes". > > When I saw "I don't see any DLLs", I did think "Oops, Microsoft Windows". > > > > Original Poster can do serveral things: > * Try to understand the build process of sigrok on Microsoft Windows. > * Share the wavedrom code to allow others build attemps (any platform) > on the new wavedrom code. > https://github.com/obiwanjacobi/libsigrok/blob/master/src/output/wavedrom.c And I might be wrong on that O.P. is developing on MSFT Windows. Cheers Geert Stappers ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
On Mon, Oct 07, 2019 at 06:25:42PM +0200, Geert Stappers wrote: > On Fri, Oct 04, 2019 at 08:50:26AM +, Marc Jacobi wrote: > > Can anyone please help me test my code? > > :-)aim for *our* code > > > > Sent: Monday, September 30, 2019 7:45 PM > > > > Okay, I have made a draft of my code - purely based on the compiler. > > > > Now I like to run it. Should I do 'make install' or is there another > > way of testing out my exporter output logic. > > > > Looking at my install of PulseView I don't see any dlls so every > > library is statically linked...? That would mean I need to pull in > > all the source code and build the UI..? > > > When I saw the "make install", I did think "yes". > > When I saw "I don't see any DLLs", I did think "Oops, Microsoft Windows". > > > > Original Poster can do serveral things: > * Try to understand the build process of sigrok on Microsoft Windows. > * Share the wavedrom code to allow others build attemps (any platform) > on the new wavedrom code. > https://github.com/obiwanjacobi/libsigrok/blob/master/src/output/wavedrom.c And I might be wrong on that O.P. is developing on MSFT Windows. Cheers Geert Stappers ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
On Fri, Oct 04, 2019 at 08:50:26AM +, Marc Jacobi wrote: > Can anyone please help me test my code? :-)aim for *our* code > Sent: Monday, September 30, 2019 7:45 PM > > Okay, I have made a draft of my code - purely based on the compiler. > > Now I like to run it. Should I do 'make install' or is there another > way of testing out my exporter output logic. > > Looking at my install of PulseView I don't see any dlls so every > library is statically linked...? That would mean I need to pull in > all the source code and build the UI..? When I saw the "make install", I did think "yes". When I saw "I don't see any DLLs", I did think "Oops, Microsoft Windows". Original Poster can do serveral things: * Try to understand the build process of sigrok on Microsoft Windows. * Share the wavedrom code to allow others build attemps (any platform) on the new wavedrom code. Regards Geert Stappers ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
Can anyone please help me test my code? Give me some pointers what to do next in order to run my exporter? Thanx, Marc From: Marc Jacobi Sent: Monday, September 30, 2019 7:45 PM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter Okay, I have made a draft of my code - purely based on the compiler. https://github.com/obiwanjacobi/libsigrok/blob/master/src/output/wavedrom.c Now I like to run it. Should I do 'make install' or is there another way of testing out my exporter output logic. Looking at my install of PulseView I don't see any dlls so every library is statically linked...? That would mean I need to pull in all the source code and build the UI..? Thanks, Marc From: Marc Jacobi Sent: Monday, September 30, 2019 11:01 AM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter Right, 'dev' - didn't think of that. Also did the dev-trick on libzip, which was also missing and that seemed to work. Configure finished - with a bunch of warnings about stuff that will not be available, but hopefully that is ok: Detected libraries (optional): - libserialport >= 0.1.1.. no - libftdi1 >= 1.0. no - hidapi >= 0.8.0. no - hidapi-hidraw >= 0.8.0.. no - hidapi-libusb >= 0.8.0.. no - bluez >= 4.0 no - libusb-1.0 >= 1.0.16 no - librevisa >= 0.0.20130412... no - libgpib. no - libieee1284. no - check >= 0.9.4.. no - glibmm-2.4 >= 2.32.0 no - python = 3.6 no - python3 = 3.6... no - python36 = 3.6.. no - python-3.6 = 3.6 no - pygobject-3.0 >= 3.0.0.. no - ruby no - ruby-... no I think I'm good for now because when I run make, I get compile errors on my new (theoretical) code I already started on ... Thanks! From: Paul Fertser Sent: Monday, September 30, 2019 9:16 AM To: Marc Jacobi Cc: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter Hey Marc :) On Mon, Sep 30, 2019 at 05:23:30AM +, Marc Jacobi wrote: > I tried installing glib-2.0 which worked (saw loads of packages being > installed). Yes, you need to install libglib2.0-dev package to get all the needed development files. HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
Okay, I have made a draft of my code - purely based on the compiler. https://github.com/obiwanjacobi/libsigrok/blob/master/src/output/wavedrom.c Now I like to run it. Should I do 'make install' or is there another way of testing out my exporter output logic. Looking at my install of PulseView I don't see any dlls so every library is statically linked...? That would mean I need to pull in all the source code and build the UI..? Thanks, Marc From: Marc Jacobi Sent: Monday, September 30, 2019 11:01 AM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter Right, 'dev' - didn't think of that. Also did the dev-trick on libzip, which was also missing and that seemed to work. Configure finished - with a bunch of warnings about stuff that will not be available, but hopefully that is ok: Detected libraries (optional): - libserialport >= 0.1.1.. no - libftdi1 >= 1.0. no - hidapi >= 0.8.0. no - hidapi-hidraw >= 0.8.0.. no - hidapi-libusb >= 0.8.0.. no - bluez >= 4.0 no - libusb-1.0 >= 1.0.16 no - librevisa >= 0.0.20130412... no - libgpib. no - libieee1284. no - check >= 0.9.4.. no - glibmm-2.4 >= 2.32.0 no - python = 3.6 no - python3 = 3.6... no - python36 = 3.6.. no - python-3.6 = 3.6 no - pygobject-3.0 >= 3.0.0.. no - ruby no - ruby-... no I think I'm good for now because when I run make, I get compile errors on my new (theoretical) code I already started on ... Thanks! From: Paul Fertser Sent: Monday, September 30, 2019 9:16 AM To: Marc Jacobi Cc: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter Hey Marc :) On Mon, Sep 30, 2019 at 05:23:30AM +, Marc Jacobi wrote: > I tried installing glib-2.0 which worked (saw loads of packages being > installed). Yes, you need to install libglib2.0-dev package to get all the needed development files. HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
Right, 'dev' - didn't think of that. Also did the dev-trick on libzip, which was also missing and that seemed to work. Configure finished - with a bunch of warnings about stuff that will not be available, but hopefully that is ok: Detected libraries (optional): - libserialport >= 0.1.1.. no - libftdi1 >= 1.0. no - hidapi >= 0.8.0. no - hidapi-hidraw >= 0.8.0.. no - hidapi-libusb >= 0.8.0.. no - bluez >= 4.0 no - libusb-1.0 >= 1.0.16 no - librevisa >= 0.0.20130412... no - libgpib. no - libieee1284. no - check >= 0.9.4.. no - glibmm-2.4 >= 2.32.0 no - python = 3.6 no - python3 = 3.6... no - python36 = 3.6.. no - python-3.6 = 3.6 no - pygobject-3.0 >= 3.0.0.. no - ruby no - ruby-... no I think I'm good for now because when I run make, I get compile errors on my new (theoretical) code I already started on ... Thanks! From: Paul Fertser Sent: Monday, September 30, 2019 9:16 AM To: Marc Jacobi Cc: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter Hey Marc :) On Mon, Sep 30, 2019 at 05:23:30AM +, Marc Jacobi wrote: > I tried installing glib-2.0 which worked (saw loads of packages being > installed). Yes, you need to install libglib2.0-dev package to get all the needed development files. HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
Hey Marc :) On Mon, Sep 30, 2019 at 05:23:30AM +, Marc Jacobi wrote: > I tried installing glib-2.0 which worked (saw loads of packages being > installed). Yes, you need to install libglib2.0-dev package to get all the needed development files. HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
Thanks Paul, that cleared it up a lot. Also had some warnings about python but I assume for now that it's okay to ignore that. This bit was left when I ran autogen.sh: Makefile.am: installing './INSTALL' Makefile.am:48: error: Libtool library used but 'LIBTOOL' is undefined Makefile.am:48: The usual way to define 'LIBTOOL' is to add 'LT_INIT' So I thought, lets see if there's a libtool package I can install, And voila! No more errors on autogen. Then I ran configure and saw this: configure: error: Package requirements (glib-2.0 >= 2.32.0 libzip >= 0.10) were not met: No package 'glib-2.0' found No package 'libzip' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. I tried installing glib-2.0 which worked (saw loads of packages being installed). Strange thing is, after this when I rerun configure it still comes back with the same error (not finding glib-2.0/libzip). Because I am using 'sudo apt install' I don't think I need to set the environment variable, do I? I feel we're almost there. If someone could help me with this last stretch... Thanks so much, Marc From: Paul Fertser Sent: Sunday, September 29, 2019 7:35 PM To: Marc Jacobi Cc: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter Hi, On Sun, Sep 29, 2019 at 07:11:07AM +, Marc Jacobi wrote: > configure.ac:99: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not > m4_defun'd You're certainly missing at least pkg-config (build dependency). Once you install it, rerun autogen.sh and show the results please. Also check that autotools versions you have are not older than the building process specifies. HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
Hi, On Sun, Sep 29, 2019 at 07:11:07AM +, Marc Jacobi wrote: > configure.ac:99: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not > m4_defun'd You're certainly missing at least pkg-config (build dependency). Once you install it, rerun autogen.sh and show the results please. Also check that autotools versions you have are not older than the building process specifies. HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
Here you can see what I'm doing: https://github.com/obiwanjacobi/libsigrok Any chance someone can help me with these tool errors? From: Marc Jacobi Sent: Saturday, September 28, 2019 7:09 PM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter In the readme is lists these steps: $ git clone git://sigrok.org/libsigrok $ cd libsigrok $ ./autogen.sh $ ./configure $ make When running the configure step I get an error: > ./configure configure: error: cannot find install-sh, install.sh, or shtool in autostuff "."/autostuff The autostuff folder that was created by autogen is empty... I am no linux user so I may be doing something simple wrong here. Do I need to install something else? BTW: I'm on win10 with ubuntu18 subsystem installed. Here's the output of autogen: ./autogen.sh autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I m4 configure.ac:99: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:99: the top level configure.ac:99: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from... m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:99: the top level configure.ac:102: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:102: the top level configure.ac:102: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from... m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:102: the top level configure.ac:105: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:105: the top level configure.ac:105: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from... m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:105: the top level configure.ac:108: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:108: the top level configure.ac:108: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from... m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:108: the top level configure.ac:119: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:119: the top level configure.ac:119: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from... m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:119: the top level configure.ac:122: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:122: the top level configure.ac:122: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from... m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:122: the top level configure.ac:125: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:125: the top level configure.ac:125: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from... m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:125: the top level configure.ac:159: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... configure.ac:159: the top level configure.ac:358: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... configure.ac:358: the top level configure.ac:405: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... configure.ac:405: the top level configure.ac:415: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... configure.ac:415: the top level configure.ac:426: warning: Missing macro AX_PYTHON_MODULE: no check for setuptools and numpy configure.ac:478: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is
Re: [sigrok-devel] Where/how to contribute an exporter
K is expanded from... ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from... m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:119: the top level configure.ac:122: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:122: the top level configure.ac:122: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from... m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:122: the top level configure.ac:125: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:125: the top level configure.ac:125: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from... m4/sigrok.m4:308: SR_ARG_OPT_PKG is expanded from... configure.ac:125: the top level configure.ac:159: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... configure.ac:159: the top level configure.ac:358: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... configure.ac:358: the top level configure.ac:405: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... configure.ac:405: the top level configure.ac:415: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... configure.ac:415: the top level configure.ac:426: warning: Missing macro AX_PYTHON_MODULE: no check for setuptools and numpy configure.ac:478: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd m4/sigrok.m4:194: SR_PKG_CHECK is expanded from... configure.ac:478: the top level configure.ac:144: error: possibly undefined macro: AC_DEFINE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:237: error: possibly undefined macro: m4_ifval configure.ac:467: error: possibly undefined macro: AC_SUBST configure.ac:582: error: possibly undefined macro: AS_MESSAGE_LOG_FD configure:6107: error: possibly undefined macro: dnl configure:6115: error: possibly undefined macro: m4_shift3 autoreconf: /usr/bin/autoconf failed with exit status: 1 From: Marc Jacobi Sent: Thursday, September 26, 2019 8:22 AM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter Beginner questions Looking at the README to find out what I need to get it building, I see a list of requirements. Do I really need all that to build!? Also when I have some code, what is an easy way to test it in the app? Marc. From: Marc Jacobi Sent: Thursday, September 26, 2019 7:28 AM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter Thanks for the pointers. Looks like 'output' is the right place. I though that interfacing with this would be handy: https://wavedrom.com/ Basically a JSON format. From: Gerhard Sittig Sent: Wednesday, September 25, 2019 9:53 PM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter On Wed, 2019-09-25 at 17:46 +, Marc Jacobi wrote: > > I am trying to research the feasibility of writing an exporter for Sigrok. > However, after scanning through several code repositories, I am unsure where > that code lives. > I was hoping to estimate the complexity by looking at the code of some of the > other exporters. See the git://sigrok.org/libsigrok repository (libsigrok is the component which contains all the device drivers and file formats) and especially the src/output/ folder there. Care to tell which export file format you plan targetting? virtually yours Gerhard Sittig -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
Beginner questions Looking at the README to find out what I need to get it building, I see a list of requirements. Do I really need all that to build!? Also when I have some code, what is an easy way to test it in the app? Marc. From: Marc Jacobi Sent: Thursday, September 26, 2019 7:28 AM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter Thanks for the pointers. Looks like 'output' is the right place. I though that interfacing with this would be handy: https://wavedrom.com/ Basically a JSON format. From: Gerhard Sittig Sent: Wednesday, September 25, 2019 9:53 PM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter On Wed, 2019-09-25 at 17:46 +, Marc Jacobi wrote: > > I am trying to research the feasibility of writing an exporter for Sigrok. > However, after scanning through several code repositories, I am unsure where > that code lives. > I was hoping to estimate the complexity by looking at the code of some of the > other exporters. See the git://sigrok.org/libsigrok repository (libsigrok is the component which contains all the device drivers and file formats) and especially the src/output/ folder there. Care to tell which export file format you plan targetting? virtually yours Gerhard Sittig -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
Thanks for the pointers. Looks like 'output' is the right place. I though that interfacing with this would be handy: https://wavedrom.com/ Basically a JSON format. From: Gerhard Sittig Sent: Wednesday, September 25, 2019 9:53 PM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Where/how to contribute an exporter On Wed, 2019-09-25 at 17:46 +, Marc Jacobi wrote: > > I am trying to research the feasibility of writing an exporter for Sigrok. > However, after scanning through several code repositories, I am unsure where > that code lives. > I was hoping to estimate the complexity by looking at the code of some of the > other exporters. See the git://sigrok.org/libsigrok repository (libsigrok is the component which contains all the device drivers and file formats) and especially the src/output/ folder there. Care to tell which export file format you plan targetting? virtually yours Gerhard Sittig -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Where/how to contribute an exporter
On Wed, 2019-09-25 at 17:46 +, Marc Jacobi wrote: > > I am trying to research the feasibility of writing an exporter for Sigrok. > However, after scanning through several code repositories, I am unsure where > that code lives. > I was hoping to estimate the complexity by looking at the code of some of the > other exporters. See the git://sigrok.org/libsigrok repository (libsigrok is the component which contains all the device drivers and file formats) and especially the src/output/ folder there. Care to tell which export file format you plan targetting? virtually yours Gerhard Sittig -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
