Question on compiling on linux

[Zachary Ware]

On Saturday, June 25, 2016, Steven Truppe <steven.truppe at chello.at> wrote:
>
> i hope this email works like you expected!

Not quite, but closer.  You've quoted me properly, but you added your
reply above the quote, so-called "top-posting".

A: Because you have to read things in reverse order.
Q: Why?
A: Top-posting.
Q: What's one of the most annoying common email practices?

But that's all rather beside the point :)

> I found the libpython3.so, i don't know why i was not able to see it,

Note that libpython3.so is very different from libpython3.5m.so:
libpython3.so is the interface to the PEP 384 stable ABI.  It does not
include the full interpreter, and is in fact just a shim that
redirects to libpython3.5m.so.  It's only really useful for building
extension modules and using the resulting binary with multiple
versions of Python.

> thank you very much to everyone wo helped me!

I'm glad we've been able to clear things up a bit!

> No my last question(s) is how can i create debug/release builds ?

Pass '--with-pydebug' to ./configure to get a debug build.  On Linux,
the difference between a debug and release build is just the
definition of debug-related macros (Py_DEBUG, _DEBUG, NDEBUG) and the
optimization level.  On Windows, another big difference in a debug
build is that it is linked against the debug CRT.  There is no such
thing on Linux, so you likely won't need a debug version of Python
just to debug your embedding app the way you would on Windows.

Hope this helps,
--
Zach