Re: [Discuss-gnuradio] OOT Module using external function

2017-05-09 Thread Ali
Hi to all, I found the below conversation. As Nathan said and explained in the link, we should write the names of .cpp files inside the CMakesList.txt file and then apply make, make install things later. It seems that we do not need to link .obj files, .cpp files are enough. https://lists.gnu.org

Re: [Discuss-gnuradio] OOT Module using external function

2017-05-08 Thread West, Nathan
I don't know what a .obj file from matlab coder is but completely ingoring that file it sounds like you need to tell cmake that the .cpp file from matlab needs to be built. On Fri, May 5, 2017 at 9:38 AM, Ali <03do...@gmail.com> wrote: > Hi, > > Under gr-TUTORIAL/lib there is myfunction_impl

Re: [Discuss-gnuradio] OOT Module using external function

2017-05-05 Thread Ali
Hi, Under gr-TUTORIAL/lib there is myfunction_impl and myfunction_impl.cc files which gr_modtool itself created. MATLAB Coder gives .h, .cpp and .obj files. I put them under the same directory(gr-TUTORIAL/lib). Then what I do is including all .h files that MATLAB generated inside two files that gr

Re: [Discuss-gnuradio] OOT Module using external function

2017-05-04 Thread West, Nathan
You have an external object that you need to link your module to. That cpp file from matlab gets compiled to an object file somehow-- you haven't specified how. Then you need to link your block to that object. On Wed, May 3, 2017 at 2:39 AM, do ber <03do...@gmail.com> wrote: > Hi to all, > > I am

[Discuss-gnuradio] OOT Module using external function

2017-05-02 Thread do ber
Hi to all, I am trying to create my own GNURadio block(OOT). I will use an external function generated by MATLAB Coder. MATLAB Coder gives the necessary .cpp and .h files. In the main module .cc file, which gr_modtool automatically creates I am including all the header files created by MATLAB Code