Probably you're in gnuradio/gr-digital instead of gnuradio/build. 

Best regards,
Marcus

Am 20. Juli 2015 12:12:20 MESZ, schrieb monika bansal <monika19...@gmail.com>:
>Hiii
>
>The previous problem is solved. Now after
>
>gr-digital % make -j4
>
>It is saying :
>make: *** No targets specified and no makefile found.  Stop.
>
>But Configuring and Generating is done.
>
>What should i do ?
>
>
>
>On Mon, Jul 20, 2015 at 3:21 PM, Marcus Müller
><marcus.muel...@ettus.com>
>wrote:
>
>>  Monika,
>>
>> obviously, there's a mistake in gr-digital/lib/CMakeLists.txt, line
>189.
>> A little more trying to solve this yourself might probably help you
>find
>> the typo; we can't tell you what you've changed, so we can't help you
>:)
>>
>> Best regards,
>> Marcus
>>
>>
>> On 20.07.2015 11:29, monika bansal wrote:
>>
>>  Hii
>>
>>  After the command :
>> gnuradio % cmake ..
>>
>>  Configuring for all other blocks except gr-digital is completed. I
>am
>> posting the output for gr-digital only :
>>
>> -- Configuring gr-digital support...
>> --   Dependency Boost_FOUND = 1
>> --   Dependency ENABLE_VOLK = ON
>> --   Dependency ENABLE_GNURADIO_RUNTIME = ON
>> --   Dependency ENABLE_GR_FFT = ON
>> --   Dependency ENABLE_GR_FILTER = ON
>> --   Dependency ENABLE_GR_BLOCKS = ON
>> --   Dependency ENABLE_GR_ANALOG = ON
>> --   Dependency ENABLE_GR_BLOCKS = ON
>> --   Dependency ENABLE_GR_FILTER = ON
>> --   Enabling gr-digital support.
>> --   Override with -DENABLE_GR_DIGITAL=ON/OFF
>> CMake Error: Error in cmake code at
>>
>>
>/home/spclab/Desktop/Monika/GNURADIO/gnuradio-3.7.5.1/gr-digital/lib/CMakeLists.txt:189:
>> Parse error.  Expected a command name, got unquoted argument with
>text
>> "${CMAKE_CURRENT_SOURCE_DIR}/qa_ofdm_chanestMMSE_vcvc.cc".
>>
>> Configuring incomplete, errors occurred!
>>
>>  What should i do ?
>>
>> On Mon, Jul 20, 2015 at 2:39 PM, Marcus Müller
><marcus.muel...@ettus.com>
>> wrote:
>>
>>>  Hi Monika,
>>>
>>> In-Tree components (like gr-digital) are meant to be built within
>the
>>> whole GNU Radio tree, so you don't make a "build/" directory under
>>> gr-digital, but under gnuradio:
>>>
>>> gr-digital % cd ..
>>> gnuradio % mkdir build
>>> gnuradio % cd build
>>> gnuradio % cmake ..
>>> gr-digital % make -j4
>>>
>>> this will build all GNU Radio. You could selectively only build
>>> gr-digital, but you will probably want to install a complete GNU
>Radio, so
>>> that doesn't really help you much.
>>>
>>> Best regards,
>>> Marcus
>>>
>>>
>>>
>>> On 20.07.2015 10:58, monika bansal wrote:
>>>
>>>   Hii
>>>
>>> After the following command :
>>>
>>> gr-digital % gr_modtool add -t general ofdm_chanestMMSE_vcvc
>>>
>>>
>>> and editing the files:  include/.h , lib/.h , lib/.cc and
>python/digital/qa_ofdm_chanest_vcvc.py
>>>
>>>
>>> I run the command
>>> gr-digital % mkdir build
>>>
>>> gr-digital % cmake ../
>>>
>>>
>>> It giving the following output :
>>>
>>> -- The C compiler identification is GNU 4.8.2
>>> -- The CXX compiler identification is GNU 4.8.2
>>> -- Check for working C compiler: /usr/bin/cc
>>> -- Check for working C compiler: /usr/bin/cc -- works
>>> -- Detecting C compiler ABI info
>>> -- Detecting C compiler ABI info - done
>>> -- Check for working CXX compiler: /usr/bin/c++
>>> -- Check for working CXX compiler: /usr/bin/c++ -- works
>>> -- Detecting CXX compiler ABI info
>>> -- Detecting CXX compiler ABI info - done
>>> CMake Error at CMakeLists.txt:23 (include):
>>>   include could not find load file:
>>>
>>>     GrBoost
>>>
>>>
>>> CMake Error at CMakeLists.txt:28 (include):
>>>   include could not find load file:
>>>
>>>     GrComponent
>>>
>>>
>>> CMake Error at CMakeLists.txt:29 (GR_REGISTER_COMPONENT):
>>>   Unknown CMake command "GR_REGISTER_COMPONENT".
>>>
>>>
>>> CMake Warning (dev) in CMakeLists.txt:
>>>   No cmake_minimum_required command is present.  A line of code such
>as
>>>
>>>     cmake_minimum_required(VERSION 2.8)
>>>
>>>   should be added at the top of the file.  The version specified may
>be lower
>>>   if you wish to support older CMake versions for this project.  For
>more
>>>   information run "cmake --help-policy CMP0000".
>>> This warning is for project developers.  Use -Wno-dev to suppress
>it.
>>>
>>> -- Configuring incomplete, errors occurred!
>>> See also
>"/home/spclab/Desktop/Monika/GNURADIO/gnuradio-3.7.5.1/gr-digital/build/CMakeFiles/CMakeOutput.log".
>>>
>>>
>>>
>>> What should i do ? have i done something wrong ?
>>>
>>>
>>>  On Sat, Jul 18, 2015 at 11:37 AM, monika bansal <
>>> <monika19...@gmail.com>monika19...@gmail.com> wrote:
>>>
>>>> yes... i will.
>>>>
>>>>  On Fri, Jul 17, 2015 at 9:48 PM, Martin Braun <
>>>> <martin.br...@ettus.com>martin.br...@ettus.com> wrote:
>>>>
>>>>>  Monika,
>>>>>
>>>>> please make sure you've gone through the tutorials at
>>>>>
>http://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorials, to
>>>>> make sure we're speaking the same terminology and all the basics
>are
>>>>> clear.
>>>>>
>>>>> Cheers,
>>>>> M
>>>>>
>>>>> On 17.07.2015 06:20, monika bansal wrote:
>>>>> > Ok... Thanks :)
>>>>> >
>>>>>   > On Fri, Jul 17, 2015 at 6:47 PM, Marcus Müller <
>>>>> <marcus.muel...@ettus.com>marcus.muel...@ettus.com
>>>>> > <mailto: <marcus.muel...@ettus.com>marcus.muel...@ettus.com>>
>wrote:
>>>>> >
>>>>> >     You can of course add that later on, but don't forget to
>change
>>>>> both
>>>>> >     your include/blockname.h, your lib/blockname_impl.h and your
>>>>> >     lib/blockname_impl.cc. If you want to work with GRC,
>remember to
>>>>> >     edit the .xml in grc/, too!
>>>>> >
>>>>> >     Best regards,
>>>>> >     Marcus
>>>>> >
>>>>> >     PS: gr_modtool doesn't do anything magical; it really just
>adds
>>>>> >     files with the content you specify. I'd like to encourage
>you to
>>>>> try
>>>>> >     around a bit more! You can't break much. And with version
>control
>>>>> >     (git) having your back, you can hardly do any harm even to
>your
>>>>> own
>>>>> >     work :)
>>>>> >
>>>>> >
>>>>> >     On 17.07.2015 14:38, monika bansal wrote:
>>>>> >>     Hii
>>>>> >>     One more doubt...
>>>>> >>     As the gr-digital / include/ ofdm_chest_vcvc.h file  have
>the
>>>>> >>     argument list given as
>>>>> >>           static sptr make(
>>>>> >>           const std::vector<gr_complex> &sync_symbol1,
>>>>> >>           const std::vector<gr_complex> &sync_symbol2,
>>>>> >>           int n_data_symbols,
>>>>> >>           int eq_noise_red_len=0,
>>>>> >>           int max_carr_offset=-1,
>>>>> >>           bool force_one_sync_symbol=false
>>>>> >>           );
>>>>> >>     Do we need to give Argument list at time of gr_modtool add
>when
>>>>> it
>>>>> >>     asks... Or we can add it later if we are not sure at the
>time of
>>>>> >>     adding new block.
>>>>> >>
>>>>> >>     On Fri, Jul 17, 2015 at 5:42 PM, monika bansal
>>>>>    >>     < <monika19...@gmail.com>monika19...@gmail.com <mailto:
>>>>> monika19...@gmail.com>> wrote:
>>>>> >>
>>>>> >>         Thanks...
>>>>> >>
>>>>> >>         On Fri, Jul 17, 2015 at 5:16 PM, Marcus Müller
>>>>> >>         <marcus.muel...@ettus.com
><mailto:marcus.muel...@ettus.com>>
>>>>> >>         wrote:
>>>>> >>
>>>>> >>             Hi Monika,
>>>>> >>
>>>>> >>             absolutely the same method:
>>>>> >>
>>>>> >>             cd gr-exisitingmodule
>>>>> >>             gr_modtool add
>>>>> >>
>>>>> >>             Note that this can only work with modules that
>follow
>>>>> >>             gr_modtool's conventions (i.e. practically only
>with
>>>>> >>             modules generated with gr_modtool in the first
>place)
>>>>> >>
>>>>> >>             Best regards,
>>>>> >>             Marcus
>>>>> >>
>>>>> >>
>>>>> >>             On 17.07.2015 13:01, monika bansal wrote:
>>>>> >>>             Hii
>>>>> >>>
>>>>> >>>             I understood how to create new module and block
>within
>>>>> >>>             this new module using gr-modtool from
>>>>> >>>
>>>>>
>http://gnuradio.org/redmine/projects/gnuradio/wiki/OutOfTreeModules.
>>>>> >>>             I want to add new block in the existing module.
>How can
>>>>> i
>>>>> >>>             do that ?
>>>>> >>>
>>>>> >>>
>>>>> >>>             _______________________________________________
>>>>> >>>             Discuss-gnuradio mailing list
>>>>> >>>             Discuss-gnuradio@gnu.org <mailto:
>>>>> Discuss-gnuradio@gnu.org>
>>>>> >>>
>>>>> <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>
>>>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>>> >>
>>>>> >>
>>>>> >>             _______________________________________________
>>>>> >>             Discuss-gnuradio mailing list
>>>>> >>              <Discuss-gnuradio@gnu.org>Discuss-gnuradio@gnu.org
>>>>> <mailto:Discuss-gnuradio@gnu.org>
>>>>> >>
>>>>> <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>
>>>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> > _______________________________________________
>>>>> > Discuss-gnuradio mailing list
>>>>> > Discuss-gnuradio@gnu.org
>>>>> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>>> >
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Discuss-gnuradio mailing list
>>>>> Discuss-gnuradio@gnu.org
>>>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>>>
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> Discuss-gnuradio mailing
>listDiscuss-gnuradio@gnu.orghttps://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>
>>>
>>>
>>> _______________________________________________
>>> Discuss-gnuradio mailing list
>>> Discuss-gnuradio@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>
>>>
>>
>>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to