I'm aware, that I could just install yet another tool "mpc" and create
them, but are the makefiles (as they are in the full release) really so
big that they couldn't simply be added to the "src" tarball? Or is it
just a philosophical thing to not include any generated files into src?

Back in the days of TAO 2.2a, the makefiles were still included, and it
was pretty convenient to just compile the libraries and not have the build
take 6+ hours for all the examples, etc.

For now, I'm merging the old makefiles from 2.2a with the new makefiles
from the complete 2.4.4 tarball, to avoid installing yet another tool,
and still end up with a less-than-8GB build dir and less-than-6-hours total build time. Maybe I cut too much, but it seems to work for my application.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

The makefiles are part of the full distribution, we generate several types, but more can be generated.

The MPC tool is part of the source distribution, you can easily run it after you set ACE_ROOT. If you just need ACE just run `$ACE_ROOT/bin/mwc.pl -type gnuace` in the ACE_wrappers/ace directory and after that say make, takes probably just a few minutes.

As you already mentioned, the source only packages only contain the original sources (which people for example import in their version management) and no generated files.

Johnny

On Friday, September 1, 2017 at 8:30:52 PM UTC+2, Andreas Leitgeb wrote:

I'm aware, that I could just install yet another tool "mpc" and create
them, but are the makefiles (as they are in the full release) really so
big that they couldn't simply be added to the "src" tarball? Or is it
just a philosophical thing to not include any generated files into src?

Back in the days of TAO 2.2a, the makefiles were still included, and it
was pretty convenient to just compile the libraries and not have the build take 6+ hours for all the examples, etc.

For now, I'm merging the old makefiles from 2.2a with the new makefiles
from the complete 2.4.4 tarball, to avoid installing yet another tool,
and still end up with a less-than-8GB build dir and less-than-6-hours total build time. Maybe I cut too much, but it seems to work for my application.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

For now, I'm merging the old makefiles from 2.2a with the new makefiles
from the complete 2.4.4 tarball, to avoid installing yet another tool,
and still end up with a less-than-8GB build dir and less-than-6-hours total build time. Maybe I cut too much, but it seems to work for my application.

Wouldn't recommend this todo, no idea whether this results in other problems later on.

Johnny

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Johnny Willemsen <jwillemsen@remedy.nl> wrote:

The MPC tool is part of the source distribution,

Oh! I missed that. Sorry for my confusion.

you can easily run it after you set ACE_ROOT. If you just need ACE just
run `$ACE_ROOT/bin/mwc.pl -type gnuace` in the ACE_wrappers/ace directory
and after that say make, takes probably just a few minutes.

I primarily need TAO (and only by dependency also ACE).
In http://www.dre.vanderbilt.edu/~schmidt/DOC_ROOT/TAO/TAO-INSTALL.html
it says: "6. Run MPC like this, $ACE_ROOT/bin/mwc.pl TAO_ACE.mwc -type gnuace"

but when I do that, it *claims* to skip some parts:
Skipping SSL_FOR_TAO (ssl_for_tao.mpc); it requires ace_for_tao.
Skipping ACE_FOR_TAO (ace_for_tao.mpc); it requires ace_for_tao.
Skipping TAO_IDL_GEN (tao_idl_fe.mpc); it requires tao_idl_fe_gen.
... (it skipped some more, but these in particular discomforted me.)

It seems like it has built libACE_SSL.so and libACE_INet_SSL.so just
fine and it is as of writing this in progress of building tao_idl,
anyway, so I'd be curious as to what exactly it is really skipping.

I'll certainly need the SSLIOP feature of TAO.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

you can easily run it after you set ACE_ROOT. If you just need ACE just
run `$ACE_ROOT/bin/mwc.pl -type gnuace` in the ACE_wrappers/ace directory and after that say make, takes probably just a few minutes.

I primarily need TAO (and only by dependency also ACE).
In http://www.dre.vanderbilt.edu/~schmidt/DOC_ROOT/TAO/TAO-INSTALL.html
it says: "6. Run MPC like this, $ACE_ROOT/bin/mwc.pl TAO_ACE.mwc -type gnuace"

but when I do that, it *claims* to skip some parts:
Skipping SSL_FOR_TAO (ssl_for_tao.mpc); it requires ace_for_tao.
Skipping ACE_FOR_TAO (ace_for_tao.mpc); it requires ace_for_tao.
Skipping TAO_IDL_GEN (tao_idl_fe.mpc); it requires tao_idl_fe_gen.
... (it skipped some more, but these in particular discomforted me.)

Skipping these is not a problem, it are projects dependent on some features that you haven't enabled. At the moment there is a real error the script will stop.

It seems like it has built libACE_SSL.so and libACE_INet_SSL.so just
fine and it is as of writing this in progress of building tao_idl,
anyway, so I'd be curious as to what exactly it is really skipping.

I'll certainly need the SSLIOP feature of TAO.

Could be that you need to set ssl=1 as feature. FYI, the next TAO micro release will add support for OpenSSL 1.1.0.

Johnny

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Johnny Willemsen <jwillemsen@remedy.nl> wrote:

Skipping SSL_FOR_TAO (ssl_for_tao.mpc); it requires ace_for_tao.
Skipping ACE_FOR_TAO (ace_for_tao.mpc); it requires ace_for_tao.
Skipping TAO_IDL_GEN (tao_idl_fe.mpc); it requires tao_idl_fe_gen.

Skipping these is not a problem, it are projects dependent on some
features that you haven't enabled. At the moment there is a real
error the script will stop.

In the meantime both TAO and the project were successfully compiled and
the (Corba-)communication tested, and it seems to be all fine.

I still don't quite understand the meaning of these skip-messages,
but given that all works fine, it's no priority to find out.
I'm however not aware of *not*-having-enabled "ace_for_tao" ;-)

When running the "server" with ssl configuration, it also writes out
a diagnostic line that looks like to mean that the whole ssl-config
had failed, yet wireshark shows me that encryption is done. (I wrote
about that a few months ago here in this newsgroup)

In a nutshell, ace and tao seem to be trigger-happy with dangerous- looking-but-harmless diagnostics ;-)

I'll certainly need the SSLIOP feature of TAO.

Could be that you need to set ssl=1 as feature.

Yes, I have it in the platform_macros.GNU, as well as
"CCFLAGS += -features=zla" as the compiler itself suggested to
add after it apparently stumbled over some zero length arrays.

FYI, the next TAO micro release will add support for OpenSSL 1.1.0.

I saw the announcement. :)
For now I'm still using the vendor's version (some 1.0.*), but I'm glad
that by the time the OS vendor's openssl here will be upgraded, then
the upgrade will likely be smooth with ace.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)