The Windows nmake files, def files and rc files for a number of ooRexx
extensions and are in main/trunk/platform/windows. What are they doing
there? If I need to locate the Windows nmake file for rxsock I would
naturally go to the main/trunk/extensions/rxsock subdir to find it (or one
of its child subdirs). The way it is currently organized I might never find
the nmake file or I might miss the fact that it also has an associated def
file.

The organization we have now is not natural, at least for me. And it also
makes the nmake files for Windows very verbose. They contain long paths to
make sources and this is naturally harder to read and maintain. By placing
the make, rc and def files close to the source files you reduce the paths
coded in the make file and reduce the amount of look up a maintainer has to
do to locate things.

Just my two cents worth :-)

Thanks,
W. David Ashley
IBM Systems and Technology Group Lab Services
Open Object Rexx Team
Mobile Phone: 512-289-7506



                                                                       
             "Rick McGuire"                                            
             <[EMAIL PROTECTED]                                         
             l.com>                                                     To
             Sent by:                  "Open Object Rexx Developer Mailing
             oorexx-devel-boun         List"                           
             [EMAIL PROTECTED]         <oorexx-devel@lists.sourceforge.net
             orge.net                  >                               
                                                                        cc
                                                                       
             08/21/2008 03:17                                      Subject
             PM                        Re: [Oorexx-devel] ooRexx SVN   
                                       Repository (main)               
                                                                       
             Please respond to                                         
             Open Object Rexx                                          
             Developer Mailing                                         
                   List                                                
             <[EMAIL PROTECTED]                                         
             ts.sourceforge.ne                                         
                    t>                                                 
                                                                       
                                                                       




I'm not sure I understand what "The *nix build for ooRexx out og the
main/trunk" is and why the location of the windows files affects the
windows builds.  The placement of those windows files was
intentionaly, as I was trying to get a clean separation between code
that's shared across platforms and code (and build files) that were
specific to just a single platform.  I'd really like to maintain that
type of separation so that anybody dealing with new platform ports
never even has to know that those files exist.

That said, I'm sure we can accommodate a few days of disruption.  I
need to spend some time working on docs and test cases now anyway.

Rick

On Thu, Aug 21, 2008 at 3:10 PM, David Ashley <[EMAIL PROTECTED]> wrote:
> All -
>
> The *nix build for ooRexx out og the main/trunk is now completely broken.
In
> looking into fixing it I found that there are a lot of Windows stuff that
> has become scattered. For instance, the .rc and .def files for a lot of
> entities are now not in the same subdir as the entity. This seems like
bad
> form and makes it very hard to find things. But if I move things around I
> know that it will break the Windows build and break it big time.
>
> So I want to get a consensus from everyone that we are at a point where
we
> can suffer a bit while we get both builds fixed. Please make your opinion
> known.
>
> BTW, the build machine will be down sometime this weekend while I update
it
> for our current build mechanism. It should not take to long to get it
back
> up but if we break both builds that should not impact anyone.
>
> Thanks,
> W. David Ashley
> IBM Systems and Technology Group Lab Services
> Open Object Rexx Team
> Mobile Phone: 512-289-7506
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

<<inline: graycol.gif>>

<<inline: pic23801.gif>>

<<inline: ecblank.gif>>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to