Re: [Discuss-gnuradio] Trouble compiling a program using GNU Radio with MSVC17 (was: Global namespace Errors with Complex and xlocNum)

[Geof Nieboer]

Melvin,

I would recommend using MSVC 2015, as I can verify that GNURadio builds fine with that, and the installation process for windows builds all dependencies with that to ensure consistency.

That way you can at least rule out a compiler difference as the reasons.  MSVC 2017 implements more of the C++11/14 standards, and (unlike GCC) doesn't provide a way to not use them, so it's *possible* it's that causing a problem.

Past that, I couldn't really comment more without the same information that Marcus was asking about, how GR was installed and how the dependencies were installed.  If you used my installers, which version did you use?  

Geof

On Thu, Mar 16, 2017 at 6:43 AM, Marcus Müller <address@hidden> wrote:

Dear Melvin,

as much as I'd like to help you with this, it's very likely not a GNU
Radio but a MSVC-related problem – Now, it's completely possible this is
*really* GNU Radio-related, so we should keep on this. However,

> UPDATE: I removed Iostream since I commented out all cin,cout lines in
> order to just have the blocks declarations and connections,  and the
> original errors returned.
If moving header includes around, and commenting out usage of cin
**introduces** errors that disappeared by moving stdafx.h to the top of
the file, my diagnosis is:

The very, very likeliest explanation for all this is some strangeness
going on in your build system (in this, case, Visual Studio).

You should probably do two things:

1. Describe how you (built? and) installed GNU Radio and other
dependencies. Is this exactly the same Visual Studio version used to
compile the dependencies (among those, especially GNU Radio)?
2. make a clean C++ project without any GNU Radio includes. Build that.
If it works, add one GNU Radio #include, but don't do anything else,
recompile. Re-construct your source code "piece by piece". Compile
early, compile often. Where exactly do things start breaking?

Note that 2. is really necessary, I'm afraid, since the errors are
definitely effect of "something in the dark, something coming from the
swamp, something elder, sinister that twists the minds of humans and
compilers alike"; also note that I hate to put this burden on you, since
it really sucks as an early C++ experience.

So, hoping this will make it possible for you to continue working on the
actual things you want to do:
Is it possible for you to try a Linux system instead, if you don't have
to install it at all, but can run it off a USB stick?

Best regards,
Marcus

On 16.03.2017 01:20, Melvin J Malave Sanchez wrote:
> ovice to c++ and the handling of library has been quite troubling.
> UPDATE: I removed Iostream since I commented out all cin,cout lines in
> order to just have the blocks declarations and connections,  and the
> original errors returned.  Ill include the flowgraph of what the code
> is supposed to resemble in case it helps.


_______________________________________________
Discuss-gnuradio mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio