Hi Maurilio,
no solution from last porter of gnu make under OS/2.
It seems to me that the problem is in make, thought, which does not
take into
account the maximum command line of the system on which it is running;
Right now we reach a maximum of 32Kb but it could be even longer and
fail on
more platforms.
So, is there a way to write current .mk file so that they don't
exceed the
smallest command line available? (in other words, remove the foreach
that
seems to be the principal cause of growing command line
requirements?).
Fighting this problem is the biggest challenge on all platforms/shells,
most of the hacks and rule duplications target just that. It's hard
(probably impossible) to find a generic solution to this. [ reasons:
a) some operations cannot be split into multiple commands, like link,
and usually splitting to multiple commands is inefficient. b) some
tools/shells don't support script files or we don't know how (* here
there is room for more research, volunteers are welcome, f.e. for
DJGPP), plus using script files hides important information from
output log, so should be avoided if possible. ]
Because all above tricks have limitations, we only use them where
possible and if absolutely required. So it's not generic.
[ maybe some things could be done to support that in more generic way
however in Harbour, maybe I'll do something if I find
time/intention. ]
In case of dynlib creation, it's a link command, which cannot be split,
so we must resort to a dynamically created script file.
We need a new technique for OS/2 to send a make var value into
a disk file. Question how, since no known methods work. I cannot
work from make documentation as OS/2 make has undocumented bugs
/ limits. Here we stand now.
It would help to see what is exactly executed on OS/2, using what
system / RTL lib calls, and/or experimenting with different tricks,
until one works. If that's not possible, we may try to employ
some dirty hacks.
One dirty hack is to pass DYNDIRLIST var (which is no bigger
than 512 bytes) to a dynamically generated OS/2 .cmd file, which
.cmd file would then pick the object list by using 'for' command
on each DYNDIRLIST item, in sync with the wildcard logic used in
dyn.mk 'ALL_OBJS := ...' line.
This solution is dirty (mainly) because it will duplicate central
make logic in .cmd batch language, and they will have to be kept
in sync. For me this is too high price to pay for this feature,
unless kept up to date by OS/2 users themselves.
Maybe there are other, better solutions.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
