[Ns-developers] Upgrade ns-3 to waf 1.6
wzssyqa at gmail.com
Sat Sep 10 08:43:04 PDT 2011
> You can be both shared and static library without any special flag, thus:
> ./waf configure -o shared .... && ./waf build
> ./waf configure --enable-static -o static .... && ./waf build
> Now "shared" build dir contains shared ns-3 code, and "static" contains the
> static version. Put the commands in a script, if needed.
> I plan to make the --enable-static-and-shared option disappear in ns 3.13
for packagers ,it's a nightmare!!!
> 1. The code to support it either a) requires extensive changes to module
> wscript files, or b) requires some complex waf hacks that tend to break
is to extensive module a bad idea ?
I don't think so.
Where are the hack ?
> 2. It clearly is not needed; a simple workaround like above takes care of
> the problem. This workaround is much more generic, as you can use it to
> produce many ns-3 builds depending on other parameters, such as python
> version, gcc version, etc.
yes, they are NEEDED!!!
> When there are two solutions to a problem, one significantly simpler to
> write and maintain than the other, we should select the simpler one.
> Can you try this, YunQiang? Clearly the problem is much easier to solve at
> the packaging scripts side, rather than in WAF. If get stuck, I would
> rather help you in your package script than in WAF side.
It's not so complex as you said.
But it does make users much more comfort.
More information about the Ns-developers