Re: [Discuss-gnuradio] OOT Block on Windows (barely feasible?)

(created a new, simple.dummy_ff() module, to keep testing simple) Still no succes, two small additions: 1. In gr-simple/CMakeList.txt (under "install directories") is written: set(GR_INCLUDE_DIR include/simple) And in gr-\swig\ CMakeList.txt is written: DESTINATION

Re: [Discuss-gnuradio] OOT Block on Windows (barely feasible?)

Imre, With the exception of the swig files, the paths things are being installed to look logical to me for the way the windows install is built. Seems like the swig files should be in include/pager2/swig based on how the tree is set up for the built-in blocks, though I can't say for certain. I

Re: [Discuss-gnuradio] OOT Block on Windows (barely feasible?)

Thanks again Geof, your hints realy helped me. After some bumps in the table (From my head), and quite some hair laying around (Also from my head); Cmake, configure, build and even install / uninstall ends with zero warnings & errors. I'll send you a .zip file by direct mail. (Be aware,

Re: [Discuss-gnuradio] OOT Block on Windows (barely feasible?)

Looks like it is trying to link to the gnuradio-pmt library and it can't find it, so check to see if the /lib subdir is being included in the library search path. Geof On Saturday, October 22, 2016, Imre Biacsics wrote: > Thank you, -o- wise one. > > In fact that was de

Re: [Discuss-gnuradio] OOT Block on Windows (barely feasible?)

Thank you, -o- wise one. In fact that was de only problem: Now i can build all projects and even build install. But the module was not properly installed and threw the: AttributeError: 'module' object has no attribute In the GRC terminal. I narrowed that down to the file /swig/pager2_swig.i

Re: [Discuss-gnuradio] OOT Block on Windows (barely feasible?)

Look in the cmake file(s) for something along the lines of: COMMAND "" If you find it, delete the double quotes. I searched and found one in cmake\Modules\UseSWIG.cmake, so I would start there. Geof On Fri, Oct 21, 2016 at 9:20 PM, Imre Biacsics wrote: > Dear

Re: [Discuss-gnuradio] OOT Block on Windows (barely feasible?)

Dear specialists, One step solved, creating two other issues. I'am sure: overlooking something very obvious. Sorry for that. The two projects throw a "Error MSB6006 "cmd.exe" exited with code 9009." Wich makes sense becease: '""' is not recognized as an internal or external command,

Re: [Discuss-gnuradio] OOT Block on Windows (barely feasible?)

Imre, Glad you had success. I'll work to replicate your steps, and then towards building a "developer pack" as an add-on to the basic install (to include adding all the many symbol files for debugging purposes). Geof On Wed, Oct 19, 2016 at 3:45 AM, Imre Biacsics wrote:

Re: [Discuss-gnuradio] OOT Block on Windows (barely feasible?)

I am going to answer my own question. "How simple is the solution when the cause is known" I was a bit dumb: Somewhere in the scripts, spaces are removed. The result was that is looked for: F:/grc/OOTmodules/ My real path : F:/grc/OOT modules/ :( sorry Imre Biacsics (Swigwin issue)

[Discuss-gnuradio] OOT Block on Windows (barely feasible?)

(Swigwin issue) Following up this message https://lists.gnu.org/archive/html/discuss-gnuradio/2016-07/msg00108.html With another question. My goal was to sort out all the dependecies and paths to succesfully automate the process. When done I will share my findings. In short, I did this:

Re: [Discuss-gnuradio] OOT Block on Windows - barely feasible

Gavin, Thanks for that. I will include your instructions, and see what I can do to make it more streamlined. Geof On Thu, Jul 7, 2016 at 2:28 PM, Gavin Jacobs wrote: > You may recall that I asked if it was feasible to build an OOT > module/block for GRC on Windows.

[Discuss-gnuradio] OOT Block on Windows - barely feasible

You may recall that I asked if it was feasible to build an OOT module/block for GRC on Windows. To answer my own question, it is barely feasible. The folks who created the windows binary package cleared the path through the jungle, but they left a lot of breadcrumbs in the resulting build. If