16 Dec
2004
16 Dec
'04
4:08 p.m.
Eric Kohl wrote:
This was perfect input. lib/win32 is because we want to have
lib/<subsys> in the future. As for static libraries, they are already in
the /lib/static directory now...I don't understand what you meant by
moving them. Your suggestion to move DLLs to a dll directory doesn't
seem bad at all, I don't know why you have the impression we wouldn't
listen. So to everyone reading the ML, is anyone objecting to this?
Really Eric, the stuff is on a WIKI, whose whole point is to be
editable. Nobody took any decisions and is leaving anyone out of anything.
Best regards,
Alex Ionescu
Alex Ionescu wrote:
We have not made a decision, we are still waiting for input.
And here's the new tree structure that we
(the devs on IRC) have
mutually agreed to, with much compromise on every camp. We would
appreciate the input of people who don't hang around, but are still
very active and part of the Project (ie Hartmut, Eric, etc).
Don't you think it's a little too late to ask for comments if you
already made a decision on IRC? This should have been discussed on the
mailing-list _only_! Please try to be considerate, it wasn't easy
getting so many people
to agree, and many of us still have reservations.
I can accept this structure but I don't really like it. IMO, the
structure is too deep, for example the lib/win32 directory doesn't
make sense to me. And I would like to move the static libraries to the
lib directory and keep all DLLs (including .kbd and .cpl files) in a
new dll directory. This way, our build system wouldn't need to process
the lib directory three times (1st run: Build static libraries. 2nd
run: Build import libraries. 3rd run: Build DLLs.)
Regards,
Eric