Hi Tamás,
On Mon, Jan 25, 2016 at 7:02 PM, Tamás Kenéz wrote:
> Gonzalo, Ray,
>
> I think your approaches are not in accordance with some CMake best practices
> (or at least what I believe they are).
Thank you for looking over my web site! I welcome comments since I am
Hi Gonzalo,
On Mon, Jan 25, 2016 at 5:22 PM, Gonzalo wrote:
>
>
> El 22/01/16 a las 10:50, Raymond Wan escribió:
>>
>> Hi Gonzalo,
>>
>> I recently tried doing this and wrote it up as a record for myself.
>> Of course, I don't know if it's the right way, but I'm doing it
El 22/01/16 a las 10:50, Raymond Wan escribió:
Hi Gonzalo,
I recently tried doing this and wrote it up as a record for myself.
Of course, I don't know if it's the right way, but I'm doing it this
way until I figure out a better way...
See if this helps and let me know if you figure out
Gonzalo, Ray,
I think your approaches are not in accordance with some CMake best
practices (or at least what I believe they are).
Please take a look at Ray's example after a heavy refactor:
https://github.com/tamaskenez/cmake-2016-jan-21-shared-lib-exe
These are the things I changed:
- In your
I have the need to have a shared library be created and then this same
library be accessed by my executable.
I want both to remain in different sibling directories and have one main
CMakeList.txt that would call the other two CMakeList.txt (one in the
lib dir, one in the exe dir) to build the
Hi Gonzalo,
On Fri, Jan 22, 2016 at 1:49 AM, Gonzalo wrote:
> I have the need to have a shared library be created and then this same
> library be accessed by my executable.
> I want both to remain in different sibling directories and have one main
> CMakeList.txt that would