Okay so, now that all my wedding stuff is offically over, here is the low down.
I was using bjam with the compile flag as listed. I am not sure what the best solution is for fixing this issue, but I imagine in the rewrite that this type of issue will be overcome.
Speaking of the re-write. Are there any initial release of the rewrite code that I could look at? From the recent traffic it souned like maybe the new code is available for review.
Thanks,
Jeff Idol
Roland Schwarz <roland.schwarz@chello.at> wrote:
Jeff Idol wrote:
> Sorry it took me so long to get back with everyone, I am getting married
> so I have been a little busy.
Congratulations!
> The following functions are causing
> compile errors in STDCALL.
>
> on_thread_exit
> on_tls_prepare
> on_process_init
> on_process_term
These functions are kind of callback functions from the C-runtime
library. However, they don't take any parameters as I can see at the
moment. So it might be possible to change them to use STDCALL as well.
But they are intended as internal interfaces to the "operating system",
so the question is why they get into your way.
It might be, that I did not properly hide away these declarations from
such changes. I will look into this.
As far as I can see at the moment this could be caused by a lack of
defensive declaration of these functions.
I think you are trying to compile with /Gz do you?
Could you please tell me how you are trying to compile the libary?
Are you using bjam? Which command line settings are you using?
> Also, what rewrite work is going on with the thread library?
The thread library is currently being rewritten mainly to get it under
the current boost license. At the same time we take the opportunity to
employ a better platform separation of the code base. No change in
interface is planned.
Roland
_______________________________________________
threads-devel mailing list
threads-devel@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/threads-devel