On Wed, Sep 16, 2015 at 9:04 PM, Robert Durkacz
wrote:
> Marcus Leech wrote "You can put "system dependencies goo" inside every
> Makefile you author..."
>
> I meant to say that I would write makefiles the way gnu make
> recommends that just work on my system.
>
> It would be nice to hear from so
Marcus Leech wrote "You can put "system dependencies goo" inside every
Makefile you author..."
I meant to say that I would write makefiles the way gnu make
recommends that just work on my system.
It would be nice to hear from someone who wants to do the same on a
different system and then we coul
On 15.09.2015 17:40, Robert Durkacz wrote:
> Certainly gnuradio is not too large a project to maintain by the make
> utility. I hope Marcus will confirm that for the benefit of people who
> never use make directly. It is for reasons of portability that you
> need a 'meta-make', right? A meta-make i
On 09/15/2015 08:40 PM, Robert Durkacz wrote:
Marcus Leech writes "When a project blooms in portability, size,
dependencies, and "reach", the use of a meta-make scheme of some sort
actually makes those kinds of project practical."
Certainly gnuradio is not too large a project to maintain by the
Marcus Leech writes "When a project blooms in portability, size,
dependencies, and "reach", the use of a meta-make scheme of some sort
actually makes those kinds of project practical."
Certainly gnuradio is not too large a project to maintain by the make
utility. I hope Marcus will confirm that fo
On 09/14/2015 10:51 PM, Robert Durkacz wrote:
Thanks Nathan for that information. If I can capture the command lines
I will be all right.
I would like to express an opinion about make. It is a clever utility.
That link shows that nearly everyone uses make in some form or
another. Whether it is c
Thanks Nathan for that information. If I can capture the command lines
I will be all right.
I would like to express an opinion about make. It is a clever utility.
That link shows that nearly everyone uses make in some form or
another. Whether it is cmake or auto-tools it would be better if
whateve
Konsole output
I never got around to porting pybombs to openSUSE and I ran into errors
on Ubuntu x86_64 and Ubuntu ARM so I have been using cmake I think since
3.6.5 and up to 3.7.8 git recently.
In the build directory.
openSUSE x86_64
---
Konsole output
cmake -DPYTHON_EXECUTABL
Hi Robert,
as Nathan pointed out, there's no formal documentation that we'd be
aware of. So let me just give you a recapitulation of the events, and
the mood back in these days when GNU Radio made the switch.
Whilst I can fully understand that you'd like to see the compiler calls
(which is possib
On Sun, Sep 13, 2015 at 7:38 AM, Robert Durkacz
wrote:
> My question is, is there some recommended way to get the command lines
> printed out as they are executed.
>
with cmake generated make files you can use make VERBOSE=1 or define the
cmake variable CMAKE_VERBOSE_MAKEFILE=On.
> Also there
I am interested in the gnuradio build system.
I last looked at gnuradio several years ago. Since then you have
adopted cmake in place of autotools.
cmake produces its own style of make files which even invoke cmake
again. When I built gnuradio I got one build error. It was difficult
to track down
On 12/13/2012 08:17 AM, wakjah ' wrote:
> Actually, I'm not sure that it was strictly necessary to remove all of
> those from the make list; I just removed what I *thought* was affecting it
> (anything that referenced if_tun.h - even if it was within a #if/#endif)
> and it seemed to work.
>
OK
Actually, I'm not sure that it was strictly necessary to remove all of
those from the make list; I just removed what I *thought* was affecting it
(anything that referenced if_tun.h - even if it was within a #if/#endif)
and it seemed to work.
With regards to posting patches... yes, I can, but I'm n
On 12/12/2012 07:40 AM, wakjah ' wrote:
> OK, so here's what I've done to get it to build:
>
> - To build gnuradio-core, comment out lines in
> D:\gnuradio\src\gnuradio-3.3.0\gnuradio-core\src\lib\io\CMakeLists.txt
> #${CMAKE_CURRENT_SOURCE_DIR}/gr_stream_pdu_base.cc
> #${CMAKE_CURRENT_S
>
> The other error that seems to crop up fairly often is that several
> things depend on linux/if_tun.h, which doesn't exist on my system. Am
> I missing a dependency?
Its used for tuntap, which is a linux only block, it should be ifdef'd out.
-josh
>
>
> Thanks,
>
> - Will
>
>
>
>
OK, so here's what I've done to get it to build:
- To build gnuradio-core, comment out lines in
D:\gnuradio\src\gnuradio-3.3.0\gnuradio-core\src\lib\io\CMakeLists.txt
#${CMAKE_CURRENT_SOURCE_DIR}/gr_stream_pdu_base.cc
#${CMAKE_CURRENT_SOURCE_DIR}/gr_stream_pdu_base.h
#gr_tuntap_pdu
Hi,
I am trying to build the output of CMake, but am getting numerous errors.
Approximately half of the projects fail to build with what I have now. Most
of these appear to be an issue with SWIG, or perhaps with what CMake has
told the compiler to feed into SWIG.
In the build log for the offendin
17 matches
Mail list logo
