C++ Building Static Library Project with a Folder Structure

I’m working on some static libraries using visual studio 2012, and after building I copy .lib and .h files to respective directories to match a desired hierarchy such as:

Should unit test be in separated repository?

Should I put unit testing stuffs in a separate repository, not in the same repository as the programming library?
So I reference the programming library as submodule.
But most open source projects that I have seen do not organize the projects like what I mention above.
Can anyone explain which approach is better?

Converting lib from other language to python and Rights issue

If I take a program, and basically translate its source from some language to python, with some small changes, can I do a entirely my new lib or I have to make a “version” of the old one?

Did C++11 address concerns passing std lib objects between dynamic/shared library boundaries? (ie dlls and so)?

One of my major complaints about C++ is how hard in practice it is to pass std library objects outside of dynamic library (ie dll/so) boundaries.

Why don’t modern libraries use OOP

I’m a beginner-level C++ programmer, but I understand the concepts of the language fairly well. When I began to learn external C++ libraries, like SDL, OpenGL (maybe something else too), to my great surprise I found out that they don’t use C++ concepts at all.

Should my small software library avoid using other libraries?

I’ve just released a small Java library that offers only a few classes and methods. Since I built the project with Maven, I immediately used several third-party libraries to achieve my goals, specifically:

Noda Time vs Joda Time?

In the Noda Time User’s Guide, the rationale section states:

Restrictions Calling DLLs Across Technologies?

I want to call a DLL in my programming language of ‘choice’. The documentation surrounding this clearly states that it must be a 32-bit DLL written in C, C++ or Delphi. But I wanted to call a DLL written in C#. It goes on to mention that the default calling mode is cdecl.

Few big libraries or many small libraries?

Over the course of some months I’ve created a little framework for game development that I currently include in all of my projects.

Big project with many external libraries – source code organisation

I was wondering what is the best way to organize my source code. I was researching on SO and found https://stackoverflow.com/a/1398594/137261 but this source code layout is library specific and doesn’t cover my situation.