From: Vincent T. <vin...@gm...> - 2012-04-05 04:42:03
|
On Thu, Apr 5, 2012 at 1:29 AM, Gustavo Sverzut Barbieri <bar...@pr...> wrote: > > as for fork()/exec, we asked you what was better to use to help > Windows. No idea if you recall, but we did ask you as our initial hope > was to go with "fork()" only solution, you said it couldn't be > supported on Windows, but the fork-exec pair could. Then we followed > that. > > >> btw, if you were doing portable code, you would use eina_file for >> shm_open and not shm_open directly > > http://git.profusion.mobi/cgit.cgi/antognolli/evas-cserve2/tree/src/bin/evas_cserve2_slave.c?h=cserve2#n200 > > Eina file does not support PROT_WRITE. We hope it can be added later, > after the current version is released. > > Here we also talked to you, you mentioned that you had some ideas to > make the shm work for windows. Right? yes, but 'you' (that is only linux coders) use ultra specific linux features. Having something in Windows which emulate more or less those features is sometimes just impossible. question : why didn't you add PROT_WRITE to eina_file ? > If you check the code, we tried to keep these isolated to aid porting. > We're just not doing the port, then it is expected to miss some cases > that will be cleared when the first port happens. there are some cross compilation toolchain to compile on all BSD, solaris and windows. It seems that you didn't use them to see what these "missed cases" are. > Don't shoot the messenger (me)! :-) the fact is : i'm fed up with you guys using linux-only features, don't care at all about other OS. There are cross compilation toolchain to check if it works or not, to port these features. You don't use it. I do. But I'm beginning to have a lot less motivation. Vincent |