OSX: building python client libs gives destructor errors:

[chadmv]

Could be an error the clang I'm using

Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn) Target: x86_64-apple-darwin12.5.0

Commenting out the lines makes it compile. But since this file is procedurally generated, makes it kind of a hassle to do that. Not sure why it would need to call a destructor on a string.

src/plow.cpp:55258:25: error: expected the class name after '~' to name a destructor
  p->name.std::string::~string();
                        ^
src/plow.cpp:55259:28: error: expected the class name after '~' to name a destructor
  p->project.std::string::~string();
                           ^
src/plow.cpp:55260:29: error: expected the class name after '~' to name a destructor
  p->username.std::string::~string();
                            ^
src/plow.cpp:55261:28: error: expected the class name after '~' to name a destructor
  p->logPath.std::string::~string();
                           ^
src/plow.cpp:57045:25: error: expected the class name after '~' to name a destructor
  p->name.std::string::~string();
                        ^
src/plow.cpp:57884:29: error: expected the class name after '~' to name a destructor
  p->cpuModel.std::string::~string();
                            ^
src/plow.cpp:57885:29: error: expected the class name after '~' to name a destructor
  p->platform.std::string::~string();
                            ^
src/plow.cpp:60166:25: error: expected the class name after '~' to name a destructor
  p->path.std::string::~string();
                        ^
src/plow.cpp:60167:29: error: expected the class name after '~' to name a destructor
  p->outputId.std::string::~string();

[justinfx]

It's a clang problem. Happened with newer versions of OSX. Use gcc:

CC=gcc CXX=g++ python setup.py build_ext --inplace

[chadmv]

Cool thanks! Maybe I'll look into eventually using CMake in the setup.py which would also help with Windows build support.

[justinfx]

We used to have a CMake build system when it was full C++ client, but then switched over to a setuptools approach when it became python. I hear waf is the new hotness?

On Sat, May 10, 2014 at 5:45 AM, Chad Vernon notifications@github.comwrote:

Cool thanks! Maybe I'll look into eventually using CMake in the setup.py which would also help with Windows build support.

— Reply to this email directly or view it on GitHubhttps://github.com/chadmv/plow/issues/2#issuecomment-42693672 .

[chadmv]

Yep clang issue.