Re: [Discuss-gnuradio] gr_modtool error when attempting to create Python tagged_stream block

Hi, Sorry, the "Answer all" button slipped my mind :) I've submitted a new issue and indicated that it's for GR 3.7. Regards Den fre 17 maj 2019 kl 17:19 skrev Müller, Marcus (CEL) : > Hi Sebastian, > in the future, could you please emails to the mailing list instead of > only to me? Others wi

Re: [Discuss-gnuradio] gr_modtool error when attempting to create Python tagged_stream block

Hi Sebastian, in the future, could you please emails to the mailing list instead of only to me? Others will be interested, too :) Thank you! Yeah, no, PyBOMBS was an attempt to solve the issue that we basically had no recent packaging on any platform. We've luckily been able to change that, or r

Re: [Discuss-gnuradio] gr_modtool error when attempting to create Python tagged_stream block

Ah, nice, so that's the latest maint-3.7 version (i.e. the latest released version). Two realizations set in: 1. Unlike 3.8-tech-preview, where we still expect a bit of breakage, this is surprising. You should definitely be able to do this. We'll look into this. If you want, you can set up an iss

Re: [Discuss-gnuradio] gr_modtool error when attempting to create Python tagged_stream block

Hi Sebastian, I know this sounds a bit silly, but could you actually tell us the version that `gnuradio-config-info --version` reports? We're kind of in the process of getting new versions out, and I'm not quite sure what different people get when they use PyBOMBS. (also, almost certain you should

[Discuss-gnuradio] gr_modtool error when attempting to create Python tagged_stream block

Hi, I get the following output when trying to create a tagged stream block with the modtool using Python as the language: https://pastebin.com/D6gKJ2aS GNURadio and gr_modtool version is the latest as installed with pybombs. Regards, Sebastian ___ Disc

Re: [Discuss-gnuradio] gr_modtool for Windows?

Hi Aaron, must admit, I haven't tried it. Technically, modtool depends on very little more than Python to do its thing. But then again, its thing is using sane compiler environments to build stuff (you can't use any of the Linux or Mac package managers as sources, obviously). And while that probab

[Discuss-gnuradio] gr_modtool for Windows?

Folks, Is there a way to install gr_modtool for Windows (10) ? Thanks in advance, Aaron Aaron Chesir The MITRE Corporation 200 Valley Road Mount Arlington, NJ 07856 w: (973) 810-0612 c: (908) 380-5798 ache...@mitre.org "Ignorance is Bliss, but Knowledge is Power" ___

[Discuss-gnuradio] gr_modtool segfault at shutdown [thrift]

Hey all, I've noticed that gr_modtool eventually segfaults on shutdown while running 'newmod' and/or 'add' (with the other options it may come up, but I don't use them as often and I also don't have a way to consistently replicate this behavior). I ran a backtrace, in this case for 'gr_modtool ad

Re: [Discuss-gnuradio] gr_modtool change - remove command aliases?

Seems like no one minds? In that case, we'll just take your suggestions! Cheers, M On 06/30/2016 05:06 PM, P wrote: > Hi, > > there is now pending patch for gr_modtool wich among other thinks > removes command aliases for this tool. > > The removal have 2 reasons. The new argument parsing syste

[Discuss-gnuradio] gr_modtool change - remove command aliases?

Hi, there is now pending patch for gr_modtool wich among other thinks removes command aliases for this tool. The removal have 2 reasons. The new argument parsing system does not support aliases without penalty. The second is I does not like them. By my opinion command aliases are mostly confusing

Re: [Discuss-gnuradio] gr_modtool consolidation question

OK thanks Marcus. Rich On Wed, May 11, 2016 at 12:40 PM, Marcus Müller wrote: > Hi Rich, > there's no such functionality directly integrated in gr_modtool. However, > there's not that many places you'll have to work when manually merging > things. > To be safe, you could just re-add all the blo

Re: [Discuss-gnuradio] gr_modtool consolidation question

Hi Rich, there's no such functionality directly integrated in gr_modtool. However, there's not that many places you'll have to work when manually merging things. To be safe, you could just re-add all the blocks you want to add to your consolidated module with "gr_modtool add", and then just overwri

[Discuss-gnuradio] gr_modtool consolidation question

Hi all, Before I fully understood how gr_modtool worked, I would make a new module for each new block I made. I would like to consolidate these disparate modules into one overarching module now. I have approx 10 modules some with more then one block that I'd like to make one module. Is there an e

Re: [Discuss-gnuradio] gr_modtool and swig

Ah glad you figured that out :) modtool should have done that for you though. Did it not? Martin On 6 May 2016 03:45, "Laur Joost" wrote: > Ask and ye shall answer: > > This happens when the public headers have virtual method declarations that > are not pure, i.e. > > virtual double samp_rate(v

Re: [Discuss-gnuradio] gr_modtool and swig

Have you nuked the build dir and tried from scratch? These kind of problems always seem to be SWIG-artifact related. M On 05/05/2016 01:01 PM, Laur Joost wrote: > Hi all! > > I've run into problems with swig in a project generated by gr_modtool. > > When I run > ctest -V -R tle_cc > the test fa

[Discuss-gnuradio] gr_modtool and swig

Hi all! I've run into problems with swig in a project generated by gr_modtool. When I run ctest -V -R tle_cc the test fails with import error: 2: Traceback (most recent call last): 2: File "/home/ec/Thesis/blocks/gr-doppler/python/qa_doppler_tle_cc.py", line 25, in 2: import doppler_swig

Re: [Discuss-gnuradio] gr_modtool rename option

On 01/07/2015 01:17 PM, Johannes Demel wrote: > I missed an option to rename a block I once created via modtool. Thus > I coded it. You can find it on github [1]. It is supposed to go Which, everyone, is the correct response to a problem such as this. > through all the created files and change al

[Discuss-gnuradio] gr_modtool rename option

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey list, I missed an option to rename a block I once created via modtool. Thus I coded it. You can find it on github [1]. It is supposed to go through all the created files and change all the old name occurrences to the new one. Also, it renames the

Re: [Discuss-gnuradio] gr_modtool enable

On Tue, May 13, 2014 at 4:04 PM, Martin Braun wrote: > On 13.05.2014 08:21, Activecat wrote: > >> We have "gr_modtool disable ABC" to disable the ABC custom block. >> But how to enable it back? >> (There is no "gr_modtool enable" or equivalent). >> > > Huh, I thought I'd put that in there. Well, s

Re: [Discuss-gnuradio] gr_modtool enable

On 13.05.2014 08:21, Activecat wrote: We have "gr_modtool disable ABC" to disable the ABC custom block. But how to enable it back? (There is no "gr_modtool enable" or equivalent). Huh, I thought I'd put that in there. Well, seems I haven't. In any case, 'disable' simply comments out all releva

[Discuss-gnuradio] gr_modtool enable

Gurus, We have "gr_modtool disable ABC" to disable the ABC custom block. But how to enable it back? (There is no "gr_modtool enable" or equivalent). ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss

Re: [Discuss-gnuradio] gr_modtool

ot;Marcus M??lle";; *Date: * Thu, Mar 6, 2014 03:43 PM *To: * "discuss-gnuradio"; *Subject: * Re: [Discuss-gnuradio] gr_modtool Hi BZS! Your question is very vague. Please do make sure to include what you actually did (in commands, where you executed them, where your module comes from.

Re: [Discuss-gnuradio] gr_modtool

Hi BZS! Your question is very vague. Please do make sure to include what you actually did (in commands, where you executed them, where your module comes from...) and what you've tried to solve your problem yourself, otherwise we will a) don't know what's the problem and b) feel like we're actu

[Discuss-gnuradio] gr_modtool

hi?? i use gr_modtool to add a new block in an exist module,it apper this : No GNU Radio module found in the given directory. Quitting. what shoud i do to solve it thanks, BZS___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.

Re: [Discuss-gnuradio] gr_modtool makexml bugs

Dear Martin, Let's refer related files as attached, thanks. List of attached files: integer_source.h integer_source_impl.h integer_source_impl.cc error_message (text file) Regards, activecat On Mon, Feb 10, 2014 at 1:19 AM, Martin Braun wrote: > On 08.02.2014 23:38, Activecat wrote:

Re: [Discuss-gnuradio] gr_modtool makexml bugs

On 08.02.2014 23:38, Activecat wrote: Dear guru, This happens intermittently. Is this a bug? Probably. That said, makexml is the most tricky part of modtool. This might be triggered by invalid code, although the error message suggests otherwise. Can you please post GNU Radio version, the in

[Discuss-gnuradio] gr_modtool makexml bugs

Dear guru, This happens intermittently. Is this a bug? Command: gr_modtool makexml integer_sink2 Output: as below Regards, activecat $ gr_modtool makexml integer_sink2 GNU Radio module name identified: activecat Warning: This is an experimental feature. Don't expect any magic. Searching for ma

Re: [Discuss-gnuradio] gr_modtool makexml fails for block coded in python

On 01/19/2014 05:12 AM, Activecat wrote: > Question: > Does "gr_modtool makexml" work with block coded in python ? Dear Activecat, no, it doesn't. This is one project I'm currently working on, but I admit it's low-priority. MB ___ Discuss-gnuradio

[Discuss-gnuradio] gr_modtool makexml fails for block coded in python

Dear Sir, In shorts, I've performed the following steps: Step (1). gr_modtool add -t sync -l python square3_ff Step (2). Edit the file "square3_ff.py" as accordingly. Step (3). gr_modtool makexml square3_ff The step (3) above fails with following message: Searching for matching files in l

Re: [Discuss-gnuradio] 'gr_modtool add' fails if new module name ends in '0'. Includes solution.

On Tue, Apr 02, 2013 at 08:30:42PM +, Monahan-Mitchell, Tim wrote: > ~/gnr$ gr_modtool newmod my_module0 > Creating out-of-tree module in ./gr-my_module0... Done. > Use 'gr_modtool add' to add a new block to this currently empty module. > ~/gnr$ cd gr-my_module0 > ~/gnr/gr-my_module0$ gr_modtoo

[Discuss-gnuradio] 'gr_modtool add' fails if new module name ends in '0'. Includes solution.

GNUradio 3.6.4.1 Ubuntu 12.04 LTS (32 bit) VMWare on Windows 7 The gr_modtool is a great help to get started. However, my module name happened to end in '0'. Try this: ~/gnr$ gr_modtool newmod my_module0 Creating out-of-tree module in ./gr-my_module0... Done. Use 'gr_modtool add' to add a new b

Re: [Discuss-gnuradio] gr_modtool cmake/make problems on OSX

On Tue, Feb 26, 2013 at 02:45:52PM +, Warren, Kevin M wrote: > Martin, > It's "howto_swig.py" that is generated following the out of tree module > tutorial (link in original post) downloaded from github. I see there's been a > new version posted within the past few hours. If the swig file w

Re: [Discuss-gnuradio] gr_modtool cmake/make problems on OSX

>>I assume you mean in the SWIG files? Or are you talking about something else? >>The SWIG order bug was fixed in both the standalone and the master branch >>version of gr-modtool. Martin, It's "howto_swig.py" that is generated following the out of tree module tutorial (link in original post)

Re: [Discuss-gnuradio] gr_modtool cmake/make problems on OSX

On Mon, Feb 25, 2013 at 08:40:31PM +, Warren, Kevin M wrote: > 1) A minor difficulty is that gr_modtool.py does not appear to be placing the > class definitions and the instantiation of the class object(s) in the proper > order. This was easy enough to remedy by hand. Hi Kevin, I assume you

Re: [Discuss-gnuradio] gr_modtool cmake/make problems on OSX

Michael, this worked perfectly, thank you so much. I'm glad there was a direct way to do it rather than poking around into the make side of things. >> sudo install_name_tool -id /opt/local/lib/libgnuradio-howto.dylib >> /opt/local/lib/libgnuradio-howto.dylib >> sudo install_name_tool -change li

Re: [Discuss-gnuradio] gr_modtool cmake/make problems on OSX

Hi Kevin - You'll want to use "install_name_tool" to fix the DLYD name id for both _howto_swig.so and libgnuradio-howto.dylib. Here's what I would do (watch wrap): {{{ sudo install_name_tool -id /opt/local/lib/libgnuradio-howto.dylib /opt/local/lib/libgnuradio-h owto.dylib sudo install_name_too

Re: [Discuss-gnuradio] gr_modtool cmake/make problems on OSX

>> The gr_modtool has been integrated into the GNU Radio master branch >> post-3.6.3, and will be part of the 3.6.4 release. At least one of the >> issues below has already been fixed. Okay, great. I saw that comment on the github README file but assumed it wasn't in the latest release sinc

Re: [Discuss-gnuradio] gr_modtool cmake/make problems on OSX

On Mon, Feb 25, 2013 at 12:40 PM, Warren, Kevin M < kevin.m.war...@vanderbilt.edu> wrote: > Greetings all, this is my first post here so I apologize ahead of time for > any clumsiness in the order and detail of my question. I'm using a Macport > install of Gnuradio 3.6.3 (system particulars below

[Discuss-gnuradio] gr_modtool cmake/make problems on OSX

Greetings all, this is my first post here so I apologize ahead of time for any clumsiness in the order and detail of my question. I'm using a Macport install of Gnuradio 3.6.3 (system particulars below). So far I've had a good deal of success with Gnuradio but I'm at the point where I need to st

Re: [Discuss-gnuradio] gr_modtool error Adding file .h

> Can you try the most current version, please. > > M > It works.Thank you for you help. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] gr_modtool error Adding file .h

On Mon, Nov 05, 2012 at 01:54:18PM +0100, Martin Braun (CEL) wrote: > On Mon, Nov 05, 2012 at 08:18:18PM +0800, Gong Zhang wrote: > > It's master which I downloaded three days ago. > > OK, that's the newest. I can't reproduce the error; it might be a > Python 2.6 thing, and I can't test that right

Re: [Discuss-gnuradio] gr_modtool error Adding file .h

On Mon, Nov 05, 2012 at 08:18:18PM +0800, Gong Zhang wrote: > It's master which I downloaded three days ago. OK, that's the newest. I can't reproduce the error; it might be a Python 2.6 thing, and I can't test that right now. I have a hunch what the problem might be, I'll get back to you when I h

Re: [Discuss-gnuradio] gr_modtool error Adding file .h

It's master which I downloaded three days ago. On Mon, Nov 5, 2012 at 09:26:32PM +0100, Martin Braun wrote: >I accidentally pushed a buggy version somewhere along the line, you must >have caught that. >Just get a new version, it should work. Which branch are you on, master >of format37? _

Re: [Discuss-gnuradio] gr_modtool error Adding file .h

I accidentally pushed a buggy version somewhere along the line, you must have caught that. Just get a new version, it should work. Which branch are you on, master of format37? M On Mon, Nov 05, 2012 at 10:27:08AM +0800, gong zhang wrote: > I'm newbie to gnuradio.I got a problem when i use the lat

[Discuss-gnuradio] gr_modtool error Adding file .h

I'm newbie to gnuradio.I got a problem when i use the latest gr_modtool to check the howto_square_ff example.I work with Ubuntu10.04,python2.6 and Cheetah2.4.4. When i excute 'gr_modtool add' I got the following: Add Python QA code? [Y/n] n Add C++ QA code? [Y/n] n Traversing lib... Adding file 'ho

[Discuss-gnuradio] gr_modtool update

Hi, couple of updates to gr_modtool. Mostly bugfixes, but there's also a new experimental feature that parses blocks, tries to guess what they're doing and then creates GRC bindings off of that information. This actually sometimes works for not too complicated blocks (what's relevant are the io si

[Discuss-gnuradio] gr_modtool update -- 3.7 format

For those using gr_modtool, I got round to updating it to the upcoming 3.7 module format. This comes with a couple of caveats, though (and one bonus), so read this before grabbing the file: * The format in 3.7 is quite different from the previous one. Filenames follow different conventions, we h

[Discuss-gnuradio] gr_modtool: disable function

Hi, a minor update to gr_modtool, you can now use $ gr_modtool disable foo_ff to disable blocks. This will uncomment them from the CMakeLists.txt, modulename_swig.i and __init__.py. As usual, available at https://github.com/mbant/gr-modtool M -- Karlsruhe Institute of Technology (KIT) Commun