That works if I force Visual C++ to generate ".o" files instead of
".obj" files. Thanks for putting me in the right direction!
I also filed a feature request.
Btw, "ozmake --debug" works fine for me. But then, I currently don't
need profiling information (-p)...
Wolfgang
Filip Konvička wrote:
Hi,
since ozmake is a make-like tool, wouldn't it suffice to build the
functor before invoking ozmake and putting the intermediate and
resulting files where ozmake expects them?
BTW, I had to tweak ozmake so that it compiles my app with the
debugging flags (-g, -p or whatever they are). Maybe contact Denis
Duchier about this, maybe he'd agree to add some more flags (this
isn't hard to do).
Cheers,
Filip
Hi all,
I am using some native functors on Windows, compiled with Visual C++.
This works without problems as long as I use oztool with the "-msvc"
option.
But now I am using ozmake, and I cannot find a way to convince ozmake
to use the "right" compiler.
In case there is no solution, I will build my native functors with a
different make tool. However, I would like ozmake to "install" the
native functors automatically (i.e. put them into the cache). So, can
I somehow tell ozmake to consider those functors during installation,
but NOT to try to build them?
Thanks for any help,
Wolfgang
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
