Comments on: First of the “other open source stuff” for Perisama http://elizabethmariesmith.com/2007/05/first-of-the-other-open-source-stuff-for-perisama/ Night is darkest just before the dawn... Sun, 07 Sep 2008 22:54:38 +0000 http://wordpress.org/?v=2.2 By: alain http://elizabethmariesmith.com/2007/05/first-of-the-other-open-source-stuff-for-perisama/#comment-44446 alain Tue, 09 Oct 2007 16:00:36 +0000 http://elizabethmariesmith.com/2007/05/first-of-the-other-open-source-stuff-for-perisama/#comment-44446 I'm trying to have openssl working under php-gtk windows. I did find your website (perisama) and thought it would have been included. I have follow the instruction from kksou website but still not luck. Do you know if openssl dll has been converted to work for php-gtk. I need to communicate through socket to a ssl website. Thanks... I’m trying to have openssl working under php-gtk windows. I did find your website (perisama) and thought it would have been included. I have follow the instruction from kksou website but still not luck.

Do you know if openssl dll has been converted to work for php-gtk. I need to communicate through socket to a ssl website.

Thanks…

]]> By: ricemaster http://elizabethmariesmith.com/2007/05/first-of-the-other-open-source-stuff-for-perisama/#comment-43954 ricemaster Thu, 04 Oct 2007 06:06:24 +0000 http://elizabethmariesmith.com/2007/05/first-of-the-other-open-source-stuff-for-perisama/#comment-43954 Hi, I'm trying to find your libiconv port on perisama.net/downloads but no success - can you point me to the file ?? Thanks Micha Hi, I’m trying to find your libiconv port on perisama.net/downloads but no success - can you point me to the file ??

Thanks
Micha

]]> By: auroraeosrose http://elizabethmariesmith.com/2007/05/first-of-the-other-open-source-stuff-for-perisama/#comment-36634 auroraeosrose Sun, 01 Jul 2007 16:52:49 +0000 http://elizabethmariesmith.com/2007/05/first-of-the-other-open-source-stuff-for-perisama/#comment-36634 Yeah, dll + windows is a real pain. One of the things I'm very careful to do with any of my builds is alter the .rc file when I build it. I add the url to perisama.net, indicate that it's a "special build" and add the compiler version used on it. This allows you to right click the dll and look at the version information to see what you're getting. I personally try to keep from dropping .dlls into my %systemroot% directory or putting them in the path unless I absolutely am forced to. Windows is generally smart enough to look in the same directory as the binary FIRST when searching for dlls and I abuse this a lot to avoid dll hell situations. Perhaps I should start adding dependency information for all the dlls I provide on perisama, I'm trying to keep users from becoming too confused on what exactly they are downloading... Yeah, dll + windows is a real pain. One of the things I’m very careful to do with any of my builds is alter the .rc file when I build it. I add the url to perisama.net, indicate that it’s a “special build” and add the compiler version used on it. This allows you to right click the dll and look at the version information to see what you’re getting.

I personally try to keep from dropping .dlls into my %systemroot% directory or putting them in the path unless I absolutely am forced to. Windows is generally smart enough to look in the same directory as the binary FIRST when searching for dlls and I abuse this a lot to avoid dll hell situations. Perhaps I should start adding dependency information for all the dlls I provide on perisama, I’m trying to keep users from becoming too confused on what exactly they are downloading…

]]> By: gaetano giunta http://elizabethmariesmith.com/2007/05/first-of-the-other-open-source-stuff-for-perisama/#comment-36453 gaetano giunta Wed, 27 Jun 2007 14:19:29 +0000 http://elizabethmariesmith.com/2007/05/first-of-the-other-open-source-stuff-for-perisama/#comment-36453 This is a really great great thing! The only problem I see with building updated versions of the "very common" unix libs and making them available on perisama is the "officialness" of the release and possible conflicts/dll hell. I have started yesterday my first php windows build - following your excellent guide for vc%2B%2B20055 express - and I had to spend a little too much time just to figure out version differences between zip.zip from edin's site and win32build from php.net. And that was after reading the extremely detailed tutorial. I also had a local copy of flex and bison as part of unxutils (which in itself is a great thing) but kinda weird: the sf.net zip package dates from 1/3/07 but the files have been built on 14/4/03) but picking the correct one was less of a problem since it's just tooling) ie. not part of the compiled-in libs. LibIconv and ssl are in fact distributed with a lot of apps (even commercial ones). Playing around with paths and testing new software I always fear to end up using an incompatible one (especially vis-a-vis the vc6-built vs. vc8-built problem). You mentioned Tor's version, gnuwin32 and edin's one. Now we will have four (if the single libs do not start appearing on apachelounge that is...). And for some of those downloads it's hard to understand what version you are getting and what are the implied dependencies... This is a really great great thing!

The only problem I see with building updated versions of the “very common” unix libs and making them available on perisama is the “officialness” of the release and possible conflicts/dll hell.

I have started yesterday my first php windows build - following your excellent guide for vc%2B%2B20055 express - and I had to spend a little too much time just to figure out version differences between zip.zip from edin’s site and win32build from php.net. And that was after reading the extremely detailed tutorial.
I also had a local copy of flex and bison as part of unxutils (which in itself is a great thing) but kinda weird: the sf.net zip package dates from 1/3/07 but the files have been built on 14/4/03) but picking the correct one was less of a problem since it’s just tooling) ie. not part of the compiled-in libs.

LibIconv and ssl are in fact distributed with a lot of apps (even commercial ones). Playing around with paths and testing new software I always fear to end up using an incompatible one (especially vis-a-vis the vc6-built vs. vc8-built problem).
You mentioned Tor’s version, gnuwin32 and edin’s one. Now we will have four (if the single libs do not start appearing on apachelounge that is…). And for some of those downloads it’s hard to understand what version you are getting and what are the implied dependencies…

]]>