(unknown)
[email protected] Thu, 24 Nov 2005 16:53:20 +0100
| Newsgroups | gmane.comp.lib.jtc |
|---|---|
| Message-ID | <OF99E1EBD8.FE0970FE-ONC12570C3.005659A3-C12570C3.0057476E@fr.world.socgen> |
Hi,
I've just downloaded and compiled the latest version of JTC Threads
package. We were using a much older version (from Waltham 2001) so I\ve
upgraded. We are experiencing memory leaks and it's thread related so I'm
hoping there are fixes in there that help me out.
So far this is what I've done.... I'm running on borland cpp builder v6
1) Downloaded and compiled the source into .lib and .dll using the existing
borland project setup here ... these dudes wrote one ages ago so I've taken
that and just thrown in the new .h and .cpp files.
2) Within my project dlls's when I try to compile I was getting fd_set
already defined and fd_set multiply defined type exceptions. I googled for
them and saw that there's some issue with multiple inclusion of winsock.h
and winsock2.h. The (ibm) site suggested I defined the preprocessor
directive _WINSOCKAPI_... so I did. and things then compiled.
I have done that and now I'm compiling each of our dll's one by one
(building here is slow and painful). I am hoping that is the correct thing
to do and that it's not anything else.
3) In one of my source files there's a call to gethostname... this compiled
problem free without the _WINSOCKAPI_ however it failed with it in there.
If I leave this out all the other code barfs with the fd_set compile error.
Right now things are compiling away... one dll after the other.. I am
defining _WINSOCKAPI_ for each compile.
I will test in about an hour or two (if I get that far) but for the moment
I'd like to know if I am on the right track. The above steps are more or
less everything Ive done.
Now I am not all that comfortable on windows in the first place (lame
excuse but true) so I'd just like to run this past this collection of users
to see if I am barking up the wrong tree. i.e. should I start again from
scratch as this approach is all wrong...or does this ring true to anybody?
Feel free to flame... if I've made a big no-no, just let me know. I'd
rather know and be flamed than not know :)
cheers
G
*************************************************************************
This message and any attachments (the "message") are confidential and intended solely for the addressee(s).
Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration.
Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified.
************
Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses
destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration.
La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie.
*************************************************************************
_______________________________________________
JTC-Users Mailing List - [email protected]
http://mail.ooc.nf.ca/mailman/listinfo/jtc-users
Visit our support FAQ before you send a message.
http://www.orbacus.com/faq/support.html