naviserver-devel

[naviserver-devel] AOLserver Work - Win32 and Other

[Jamie R. <jra...@sb...>]

Hello Everyone,
  For a while I've been maintaining a private build of
AOLserver, with a mix of custom modules / new features
/ Win32 fixes / bug fixes.  Several of these were done
while I was working for Alex Hisen, who runs a number
of production AOLserver sites on Windows.  (Jeff Huber
also contributed.)  Since carrying these patches
forward to new versions is onerous, Alex and I would
like to see them incorporated into stock AOLserver
and/or NaviServer before the codebases diverge too
greatly.
  If you're interested, a list of the changes is at:
http://www.jamierasmussen.com/download/AM-AOLserver-Changes.txt
  Some of these were reported on SourceForge but not
commented on, so I don't know their worth.  AOLserver
is mostly a hobby for me now, so I haven't had time to
follow up as much as I would like.  Most recently I've
been playing with the new build system, and have a
script to help download and build the many
dependencies for a "batteries-included" windows
distribution.
  I haven't had a chance to evaluate NaviServer on
Win32 yet, but it seems like you're doing some really
neat stuff, so I'm looking forward to it.  In the
meantime, if you'd like any more information on what
we have, please let me know.
Thanks!

Jamie

Re: [naviserver-devel] AOLserver Work - Win32 and Other

[Zoran V. <zv...@ar...>]

Am 11.01.2006 um 06:35 schrieb Jamie Rasmussen:

> Hello Everyone,
>   For a while I've been maintaining a private build of
> AOLserver, with a mix of custom modules / new features
> / Win32 fixes / bug fixes.  Several of these were done
> while I was working for Alex Hisen, who runs a number
> of production AOLserver sites on Windows.  (Jeff Huber
> also contributed.)  Since carrying these patches
> forward to new versions is onerous, Alex and I would
> like to see them incorporated into stock AOLserver
> and/or NaviServer before the codebases diverge too
> greatly.
>   If you're interested, a list of the changes is at:
> http://www.jamierasmussen.com/download/AM-AOLserver-Changes.txt
>   Some of these were reported on SourceForge but not
> commented on, so I don't know their worth.  AOLserver
> is mostly a hobby for me now, so I haven't had time to
> follow up as much as I would like.  Most recently I've
> been playing with the new build system, and have a
> script to help download and build the many
> dependencies for a "batteries-included" windows
> distribution.
>   I haven't had a chance to evaluate NaviServer on
> Win32 yet, but it seems like you're doing some really
> neat stuff, so I'm looking forward to it.  In the
> meantime, if you'd like any more information on what
> we have, please let me know.
> Thanks!
>

Hi Jamie!

Nice to hear from you again!

I am very interested to have a Win-expert on the board.
I do not know about others but we, as you probably know,
ship a product based on the NS for Unices (Sol/Linux,Mac)
and Windows. At the moment most of the developers in the
NS camp (well to be honest all except one) have mostly
Unix experience. To have more people handling the Win part
would be a great relief for us.

I suggest the following, if you agree: we add you as developer,
you check-in your patches into RFE, we go thru them together
and apply them after examination.  This RFE check-in is needed
so we can better track what has been adopted in the server and
what not. This is not a commit-barrier, just a small admin
burden to get things better organized.

The NS code is based on AS 4.0. This is about one year ago
and since then we have been constantly improving it and adding
features.

What do you think?

Cheers
Zoran

Re: [naviserver-devel] AOLserver Work - Win32 and Other

[Jamie R. <jra...@sb...>]

> Hi Jamie!
> 
> Nice to hear from you again!
> 
> I am very interested to have a Win-expert on the
> board.
> I do not know about others but we, as you probably
> know,
> ship a product based on the NS for Unices
> (Sol/Linux,Mac)
> and Windows. At the moment most of the developers in
> the
> NS camp (well to be honest all except one) have
> mostly
> Unix experience. To have more people handling the
> Win part
> would be a great relief for us.
> 
> I suggest the following, if you agree: we add you as
> developer,
> you check-in your patches into RFE, we go thru them
> together
> and apply them after examination.  This RFE check-in
> is needed
> so we can better track what has been adopted in the
> server and
> what not. This is not a commit-barrier, just a small
> admin
> burden to get things better organized.
> 
> The NS code is based on AS 4.0. This is about one
> year ago
> and since then we have been constantly improving it
> and adding
> features.
> 
> What do you think?

Sounds good to me, my SourceForge ID is jrasmuss23. 
I'll start looking at merging patches over.
Thanks!

Jamie

Re: [naviserver-devel] AOLserver Work - Win32 and Other

[Zoran V. <zv...@ar...>]

Am 11.01.2006 um 17:53 schrieb Jamie Rasmussen:

> Sounds good to me, my SourceForge ID is jrasmuss23.

You are in.

Cheers
Zoran

[naviserver-devel] Win32 build problems

[Jamie R. <jra...@sb...>]

I took a look at the NaviServer HEAD and the Win32 build is broken in 
several places.

On this machine I have Visual Studio 6, Visual C++ Toolkit 2003, and 
Visual Studio 2005.  The build files in CVS are for Visual Studio 6 and 
Visual Studio .NET 2003.  I'm not sure if it is worth spending time on 
the VS6 build files.  The 2003 Toolkit is command-line only, but is 
free-to-download.  Visual Studio 2005 has some nice features, but since 
it was just released I don't know how many people have started using it. 
  Unfortunately, there appear to be problems no matter which version you 
start with. :-)

I tried VS2005 first, since Microsoft has stopped mainstream support for 
VS6, so e.g. recent Platform SDKs don't work with it.  There are a 
number of issues using VS2005, starting with TCL patch #1096916.  I 
think it was only applied to the 8.5 branch.  When building I think we 
would want to define:
_CRT_SECURE_COPP_OVERLOAD_STANDARD_NAMES=1
_CRT_SECURE_NO_DEPRECATE=1
_CRT_NONSTDC_NO_DEPRECATE=1
and potentially
_USE_32BIT_TIME_T=1

I tried Visual Studio 6, but there I had problems there with an old 
version of Ws2tcpip.h being used; that may just be how I have my include 
path set up, I'd have to investigate further.  It causes problems in 
dns.c at least.

There are also a number of problems not specific to the compiler version:

nsthread/compat.c, getopt.c, and tclatclose.c are gone.  task.c, 
tclcache.c, tcltime.c, and url2file.c have been added.  These changes 
need to be reflected in the build files.

The #define's for NS_MAJOR_VERSION etc. were removed from ns.h but are 
still needed by the Windows build.

Visual Studio doesn't allow mixed declarations and code for .c files, so 
in urlspace.c line 1431 we need to move the "doit" declaration to the 
top of JunctionFind.

The new code in binder.c will need a number of additional ifdef's to 
compile on Win32.

The tcl debug suffix changed from "d" to "g" some time ago, this should 
be reflected in the post-build copy instructions.

As I mentioned in my earlier post, the AOLserver HEAD now has a unified 
command line build system, it might be worth taking a closer look at that...
Thanks,

Jamie

Re: [naviserver-devel] Win32 build problems

[Zoran V. <zv...@ar...>]

Am 13.01.2006 um 09:29 schrieb Jamie Rasmussen:

> I took a look at the NaviServer HEAD and the Win32 build is broken  
> in several places.

Hm... we regulary build NS on Windows... I will pass this to
my collegue who is attending this part. Perhaps he didn't
checkin the latest updates...

Zoran

>
> On this machine I have Visual Studio 6, Visual C++ Toolkit 2003,  
> and Visual Studio 2005.  The build files in CVS are for Visual  
> Studio 6 and Visual Studio .NET 2003.  I'm not sure if it is worth  
> spending time on the VS6 build files.  The 2003 Toolkit is command- 
> line only, but is free-to-download.  Visual Studio 2005 has some  
> nice features, but since it was just released I don't know how many  
> people have started using it.  Unfortunately, there appear to be  
> problems no matter which version you start with. :-)
>
> I tried VS2005 first, since Microsoft has stopped mainstream  
> support for VS6, so e.g. recent Platform SDKs don't work with it.   
> There are a number of issues using VS2005, starting with TCL patch  
> #1096916.  I think it was only applied to the 8.5 branch.  When  
> building I think we would want to define:
> _CRT_SECURE_COPP_OVERLOAD_STANDARD_NAMES=1
> _CRT_SECURE_NO_DEPRECATE=1
> _CRT_NONSTDC_NO_DEPRECATE=1
> and potentially
> _USE_32BIT_TIME_T=1
>
> I tried Visual Studio 6, but there I had problems there with an old  
> version of Ws2tcpip.h being used; that may just be how I have my  
> include path set up, I'd have to investigate further.  It causes  
> problems in dns.c at least.
>
> There are also a number of problems not specific to the compiler  
> version:
>
> nsthread/compat.c, getopt.c, and tclatclose.c are gone.  task.c,  
> tclcache.c, tcltime.c, and url2file.c have been added.  These  
> changes need to be reflected in the build files.
>
> The #define's for NS_MAJOR_VERSION etc. were removed from ns.h but  
> are still needed by the Windows build.
>
> Visual Studio doesn't allow mixed declarations and code for .c  
> files, so in urlspace.c line 1431 we need to move the "doit"  
> declaration to the top of JunctionFind.
>
> The new code in binder.c will need a number of additional ifdef's  
> to compile on Win32.
>
> The tcl debug suffix changed from "d" to "g" some time ago, this  
> should be reflected in the post-build copy instructions.
>
> As I mentioned in my earlier post, the AOLserver HEAD now has a  
> unified command line build system, it might be worth taking a  
> closer look at that...
> Thanks,
>
> Jamie
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through  
> log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD  
> SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel

Re: [naviserver-devel] Win32 build problems

[Ibrahim T. <it...@we...>]

Hi Jamie,

Have you taken a look at the Visual Studio projects (files *.sln, 
*.dsp, *.dsw).

Although we do compile for Windows, I haven't had the time to go 
through all the build files and variants (especially not the 
command line Makefiles and stuff).

I currently use the VS 2003 .NET  and the naviserver.sln project. 
This works and build fine for us (at least for the parts of the 
naviserver and libs we employ).

Ibrahim


Zoran Vasiljevic wrote:
> 
> Am 13.01.2006 um 09:29 schrieb Jamie Rasmussen:
> 
>> I took a look at the NaviServer HEAD and the Win32 build is broken  in 
>> several places.
> 
> 
> Hm... we regulary build NS on Windows... I will pass this to
> my collegue who is attending this part. Perhaps he didn't
> checkin the latest updates...
> 
> Zoran