Hi, Michael.


>How did you unzip the src.tgz file? Winzip does the conversion
automatically.
I am using WindowsCommander which has built-in support for many archive
types including tgz. If you say that WinZip does the conversion
automatically -
great, one question less :-)

>The quogen executables should reside in the $QUO_ROOT/codegen directory.
Ok.

>In the last couple of months, we tried to get away from generating files in
directories
>that are not self-contained. Along these lines, we should generate
allQuoKernel libraries
>and dlls in $QUO_ROOT/quo, and change the dsp files that use them
accordingly. The
>same holds true for $QUO_ROOT/codegen
In general, I understand your point, but could you please explain what do
you mean
by "self-contained". The small problem I see - currently, for example
quogen, depends
only on ace.lib/dll. If in future you will come up with some kind of common
library and
will put this library also in own directory, it will be difficult to invoke
quogen from another
projects (examples or something else) because required .dll library will not
be found.
The only way to handle such a situation is to update PATH variable. If there
will be more
then one such common library, it could be slightly inconvenient.

>If you can work in my comments, I'd be happy integrate all your DSP files
into the QuO release.
You can download dsp and dsw files with my modifications from:
http://www.geocities.com/andreynech/Projects/quo_dsps.zip

In this archive:

* Modified project files for quogen - quogen.exe and quogend.exe are
generated
in $QUO_ROOT/codegen.

* Modified project files for quoKernel - libQuoKernel.dll and
libQuoKerneld.dll with corresponding
.lib files are generated into $QUO_ROOT/quo directory.

* There are also project files for simple/adapter example which illustrate
the problem I
mentioned in my previous mail.


Thank you.

Andrey.

--
[To unsubscribe to this list send an email to "majdart@..."
with the following text in the BODY of the message "unsubscribe quo-users"]