On Friday, 31 October 2014 at 09:51:09 UTC, nomi wrote:
Also I think you are mistaking where the are actually
used. Theare used in CUDA code, not in C++ code. While
CUDA is a variation on C++, it is still not C++ and has to pass
through a special parser that splits out the host code and the
gpu
On Thursday, 27 November 2014 at 08:47:32 UTC, nomi wrote:
On Friday, 31 October 2014 at 09:51:09 UTC, nomi wrote:
Also I think you are mistaking where the are actually
used. Theare used in CUDA code, not in C++ code. While
CUDA is a variation on C++, it is still not C++ and has to pass
On 11/01/2014 10:02 PM, Nordlöw wrote:
Could you add a reference on how to DUB-build a library as dynamic
instead of static library to easy the process for newcomers?
Not really, as I said in the article.
Shared libraries are still a bit cumbersome to use with dub though.
Basically I just
On Thursday, 30 October 2014 at 01:02:40 UTC, Martin Nowak wrote:
https://code.dawg.eu/reducing-vibed-turnaround-time-part-1-faster-linking.html
Could you add a reference on how to DUB-build a library as
dynamic instead of static library to easy the process for
newcomers?
Also I think you are mistaking where the are actually
used. The are used in CUDA code, not in C++ code. While
CUDA is a variation on C++, it is still not C++ and has to pass
through a special parser that splits out the host code and the
gpu code to be compiled.
__
adil
On Thursday, 30 October 2014 at 01:02:40 UTC, Martin Nowak wrote:
This is the first post on my new blog https://code.dawg.eu/.
It starts with a 3 part series on reducing vibe.d turnaround
times during development.
https://code.dawg.eu/reducing-vibed-turnaround-time-part-1-faster-linking.html
This is the first post on my new blog https://code.dawg.eu/.
It starts with a 3 part series on reducing vibe.d turnaround times
during development.
https://code.dawg.eu/reducing-vibed-turnaround-time-part-1-faster-linking.html
There is also a friendly comment system.
