|
From: Stefan J. <st...@gr...> - 2006-08-29 08:23:58
|
Am Di, 29.08.2006, 10:11, schrieb asco developer: Hello João, >> No, this is not the problem. There will be always a hostname (at least >> named localhost or something). But when using gethostname() you'll need >> additional checks for certain headers and libraries on different >> platforms *just for this one little function*. > > Hello Stefan, > > I was unaware of this issue. Just for enlightenment, can you please > give me examples of such additional checks that are necessary? Also, > on which platforms does this happens? I do not know this right now. Haven't got it kept in mind... One example: In mingw32 (Win32) you need even more: #include <winsock2.h> then you need to start the networking api with some call. Also you need -lwsock32 on the linker line. On Solaris you'll need also some other libraries, etc., etc. Anyway. It's not about to really handle this. It is just useless overhead for a program to find out the output files of ASCO by determining the hostname. It should be possible to let the program pass the filename to ASCO. That is much! more convenient. On the other hand ASCO itself can remain using hostnames for "intermediate" files in order not to get confused about different machines involved in optimization. Cheers, Stefan. |