[ace-users] ACE install question
Douglas Atique
I am not using a PRF form because this question is very direct, but I will try to provide all information here.
On building ACE 5.6.4 with MinGW 5.1.4 and Msys 1.0.10 on Windows, I would like to be able to do make install and have ACE libraries, headers, executables, etc. installed to some path. The purpose is to be able to build ACE once and use it as a third-party library to build other applications. There are many files in the ACE source tarball that are not needed to use it as a library and that add a lot to the overall package size. Is there a list of files I could use to copy files manually if I want to?
Best regards,
Douglas Atique
Douglas C. Schmidt
Hi Douglas,
I think you can do this if you build ACE using the autoconf option.
Thanks,
Doug
Chad Elliott
Douglas Atique wrote:
> Dear all,
>
> I am not using a PRF form because this question is very direct, but I
> will try to provide all information here.
> On building ACE 5.6.4 with MinGW 5.1.4 and Msys 1.0.10 on Windows, I
> would like to be able to do make install and have ACE libraries,
> headers, executables, etc. installed to some path. The purpose is to
> be able to build ACE once and use it as a third-party library to build
> other applications. There are many files in the ACE source tarball
> that are not needed to use it as a library and that add a lot to the
> overall package size. Is there a list of files I could use to copy
> files manually if I want to?
You may be able to do this with MPC. You would have to regenerate the
GNU makefiles with MPC using the following:
cd %ACE_ROOT%
%ACE_ROOT%\bin\mwc.pl -type gnuace -genins
Then after building, you can use prj_install.pl from %MPC_ROOT% or
%ACE_ROOT%\MPC.
HTH,
Chad Elliott
Object Computing, Inc.
>
> Best regards,
> Douglas Atique
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> ace-users mailing list
> ace-...@list.isis.vanderbilt.edu
> http://list.isis.vanderbilt.edu/mailman/listinfo/ace-users
Johnny Willemsen
> You may be able to do this with MPC. You would have to regenerate the
> GNU makefiles with MPC using the following:
>
> cd %ACE_ROOT%
> %ACE_ROOT%\bin\mwc.pl -type gnuace -genins
>
> Then after building, you can use prj_install.pl from %MPC_ROOT% or
> %ACE_ROOT%\MPC.
Would this be something to shop as part of the ACE/TAO distribution?
Generate the ins files as part of the package?
Johnny
Chad Elliott
Possibly, but it would probably only be beneficial for the core
libraries of ACE and TAO (and CIAO). For distribution, MPC is used to
generate everything so I don't know if it's a good choice for use during
the creation of distribution makefiles.
If the GNUmakefiles ever get a real "install" target, this wouldn't be
necessary except when ACE/TAO is built by something other than a
makefile (i.e., Visual Studio).
Chad
> Johnny
>
>
Johnny Willemsen
> Possibly, but it would probably only be beneficial for the core
> libraries of ACE and TAO (and CIAO). For distribution, MPC is used to
> generate everything so I don't know if it's a good choice for use
> during
> the creation of distribution makefiles.
No, then it is not an option. It seems the ins files are tied to a real
generator, would it be possible to just run -gendir for TAO_ACE.mwc, that
would generate the install files for just the core libs/tools
> If the GNUmakefiles ever get a real "install" target, this wouldn't be
> necessary except when ACE/TAO is built by something other than a
> makefile (i.e., Visual Studio).
The borland type has an install target. The install target issue seems to
appear each month but nobody is willing to fund such an addition.
Johnny
Chad Elliott
> Hi,
>
>
>> Possibly, but it would probably only be beneficial for the core
>> libraries of ACE and TAO (and CIAO). For distribution, MPC is used to
>> generate everything so I don't know if it's a good choice for use
>> during
>> the creation of distribution makefiles.
>>
>
> No, then it is not an option. It seems the ins files are tied to a real
> generator, would it be possible to just run -gendir for TAO_ACE.mwc, that
> would generate the install files for just the core libs/tools
>
Yes, if files are added dependent upon the project type then the .ins
file will be tied to that project type. And yes, -genins for
TAO_ACE.mwc would get just the core libs and tools.
>
>> If the GNUmakefiles ever get a real "install" target, this wouldn't be
>> necessary except when ACE/TAO is built by something other than a
>> makefile (i.e., Visual Studio).
>>
>
> The borland type has an install target. The install target issue seems to
> appear each month but nobody is willing to fund such an addition.
>
Yep, I guess it's not a priority.
Chad
> Johnny
>
>
Douglas Atique
Thanks for your reply.
A question on MPC. When building ACE_SSL mwc.pl says ssl is skipped. I have found out about the global.features files, but there are 2 of them in the distribution. Which one is in effect? Should I just set ssl=1 in one of them?
Anyway, I have successfully regenerated the makefiles as you described and rebuilt ACE 5.6.5 with MinGW. However, when running
MPC/prj_install.pl /c/ACE-5.6.5 .
the resulting installation directory does not contain any DLLs. Only .h, .inl and .cpp files have been copied. Is this correct? Should I copy them by hand? Should I copy anything else by hand?
Thanks a lot!
-- Douglas
Chad Elliott <elli...@ociweb.com> wrote:
Hi Douglas,
Douglas Atique wrote:
> Dear all,
>
> I am not using a PRF form because this question is very direct, but I
> will try to provide all information here.
> On building ACE 5.6.4 with MinGW 5.1.4 and Msys 1.0.10 on Windows, I
> would like to be able to do make install and have ACE libraries,
> headers, executables, etc. installed to some path. The purpose is to
> be able to build ACE once and use it as a third-party library to build
> other applications. There are many files in the ACE source tarball
> that are not needed to use it as a library and that add a lot to the
> overall package size. Is there a list of files I could use to copy
> files manually if I want to?
You may be able to do this with MPC. You would have to regenerate the
GNU makefiles with MPC using the following:
cd %ACE_ROOT%
%ACE_ROOT%\bin\mwc.pl -type gnuace -genins
Then after building, you can use prj_install.pl from %MPC_ROOT% or
%ACE_ROOT%\MPC.
Douglas Atique
Thanks for your reply.
I haven't tried autoconf install for a while. Is it functional for mingw?
Thanks,
Douglas
"Douglas C. Schmidt" <sch...@dre.vanderbilt.edu> wrote:
Hi Douglas,
> I am not using a PRF form because this question is very direct, but I
> will try to provide all information here. On building ACE 5.6.4 with
> MinGW 5.1.4 and Msys 1.0.10 on Windows, I would like to be able to do
> make install and have ACE libraries, headers, executables,
> etc. installed to some path. The purpose is to be able to build ACE
> once and use it as a third-party library to build other
> applications. There are many files in the ACE source tarball that are
> not needed to use it as a library and that add a lot to the overall
> package size. Is there a list of files I could use to copy files
> manually if I want to?
Chad Elliott
Douglas Atique wrote:
> Hi Chad,
> Thanks for your reply.
>
> A question on MPC. When building ACE_SSL mwc.pl says ssl is skipped. I
> have found out about the global.features files, but there are 2 of
> them in the distribution. Which one is in effect? Should I just set
> ssl=1 in one of them?
The one in $ACE_ROOT/bin/MakeProjectCreator/config is the one in effect,
but you shouldn't edit either of them.
You should create a file in
$ACE_ROOT/bin/MakeProjectCreator/config/default.features with the contents:
ssl=1
>
> Anyway, I have successfully regenerated the makefiles as you described
> and rebuilt ACE 5.6.5 with MinGW. However, when running
> MPC/prj_install.pl /c/ACE-5.6.5 .
> the resulting installation directory does not contain any DLLs. Only
> .h, .inl and .cpp files have been copied. Is this correct? Should I
> copy them by hand? Should I copy anything else by hand?
If you didn't provide any options, then this is what should be
expected. If you want to install DLL's in addition to all of the other
things that are installed by default, you need to run it using the
following:
MPC/prj_install.pl -a lib_output /c/ACE-5.6.5 .
Unfortunately, I just realized that this isn't clearly documented. The
script hasn't had much use (as far as I can tell).
HTH,
Chad
>
> Thanks a lot!
> -- Douglas
>
> */Chad Elliott <elli...@ociweb.com>/* wrote:
>
> Hi Douglas,
>
> Douglas Atique wrote:
> > Dear all,
> >
> > I am not using a PRF form because this question is very direct,
> but I
> > will try to provide all information here.
> > On building ACE 5.6.4 with MinGW 5.1.4 and Msys 1.0.10 on
> Windows, I
> > would like to be able to do make install and have ACE libraries,
> > headers, executables, etc. installed to some path. The purpose
> is to
> > be able to build ACE once and use it as a third-party library to
> build
> > other applications. There are many files in the ACE source tarball
> > that are not needed to use it as a library and that add a lot to
> the
> > overall package size. Is there a list of files I could use to copy
> > files manually if I want to?
>
Douglas C. Schmidt
Hi Douglas,
> Thanks for your reply.
> I haven't tried autoconf install for a while. Is it functional for mingw?
Good question - please give it a shot to see how it works.
Thanks,
Doug
Chad Elliott
> Hi Douglas,
>
> Douglas Atique wrote:
>
>> Hi Chad,
>> Thanks for your reply.
>>
>> A question on MPC. When building ACE_SSL mwc.pl says ssl is skipped. I
>> have found out about the global.features files, but there are 2 of
>> them in the distribution. Which one is in effect? Should I just set
>> ssl=1 in one of them?
>>
>
> The one in $ACE_ROOT/bin/MakeProjectCreator/config is the one in effect,
> but you shouldn't edit either of them.
>
> You should create a file in
> $ACE_ROOT/bin/MakeProjectCreator/config/default.features with the contents:
>
Just in case it wasn't clear, the file you should make is called
default.features and should be placed in
$ACE_ROOT/bin/MakeProjectCreator/config.
Thanks,
Chad
Douglas Atique
Will pursue further Chad's approach.
Thanks!
Douglas C. Schmidt
Hi Vassili,
Thanks very much for your email. Please make sure to send all
questions related to TAO or ACE to the ACE mailing list or ACE+TAO
newsgroup, rather than to me directly since I travel frequently and
often don't have ready access to email. See
http://www.cs.wustl.edu/~schmidt/ACE-mail.html
for more info on how to access these resources.
> I try to use Logger exemple and something is wrong with message data
> from Pocket PC 2003 client. Server has a first char of message "m"
> when I use "Logger Client" from PPC2003. Server can get a full
> message text "message 1" from "Logger Client" installed in PC(WINXP).
To ensure that we have proper version/platform/compiler information,
please make sure you fill out the appropriate problem report form (PRF),
which is in
$ACE_ROOT/PROBLEM-REPORT-FORM
$TAO_ROOT/PROBLEM-REPORT-FORM
or in
$ACE_ROOT/BUG-REPORT-FORM
$TAO_ROOT/BUG-REPORT-FORM
in older versions of ACE+TAO. Make sure to include this information
when asking any questions about ACE+TAO since otherwise we have to
"guess" what version/platform/compiler/options you've using, which is
very error-prone and slows down our responsiveness. If you don't use
the PRF, therefore, it is less likely that someone from the core
ACE+TAO developer team will be able to answer your question.
Naturally, we encourage and appreciate other members of the ACE+TAO
user community who can respond to questions that they have the answers
to.
Please note, moreover, that the DOC groups at Washington University,
UC Irvine, and Vanderbilt University only provide "best effort"
support for non-sponsors who are using the latest release, as
described in
http://www.dre.vanderbilt.edu/~schmidt/DOC_ROOT/ACE/docs/ACE-bug-process.html
Therefore, please make sure you are using ACE+TAO+CIAO x.6.4 (i.e.,
ACE 5.6.4, TAO 1.6.4, and CIAO 0.6.4), which you can download from
http://download.dre.vanderbilt.edu
under the heading: "Latest Micro Release Kit". If you need more
"predictable" help or need help for earlier versions of ACE+TAO+CIAO
please see
http://www.dre.vanderbilt.edu/support.html
for a list of companies that will provide you with ACE+TAO+CIAO
commercial support.
Thanks,
Doug
Steve Huston
> > I try to use Logger exemple and something is wrong with message
data
> > from Pocket PC 2003 client. Server has a first char of message
"m"
> > when I use "Logger Client" from PPC2003. Server can get a full
> > message text "message 1" from "Logger Client" installed in
> PC(WINXP).
Be aware that Pocket PC uses Unicode, not plain ASCII. You're probably
seeing a multiple-byte 'm'.
-Steve
Douglas Atique
-a lib_output doesn't seem to have made any difference. After running prj_install as you say, I run
find . -name "*.dll" and get nothing. Should I run something else with mwc.pl to get some ins file to be generated for the DLLs? Am I missing something else?
The default.features file worked ok, thanks. Now ACE_SSL doesn't get skipped anymore.
Cheers,
Doug
Chad Elliott <elli...@ociweb.com> wrote:
Hi Douglas,
Douglas Atique wrote:
> Hi Chad,
> Thanks for your reply.
>
> A question on MPC. When building ACE_SSL mwc.pl says ssl is skipped. I
> have found out about the global.features files, but there are 2 of
> them in the distribution. Which one is in effect? Should I just set
> ssl=1 in one of them?
The one in $ACE_ROOT/bin/MakeProjectCreator/config is the one in effect,
but you shouldn't edit either of them.
You should create a file in
$ACE_ROOT/bin/MakeProjectCreator/config/default.features with the contents:
ssl=1
>
> Anyway, I have successfully regenerated the makefiles as you described
> and rebuilt ACE 5.6.5 with MinGW. However, when running
> MPC/prj_install.pl /c/ACE-5.6.5 .
> the resulting installation directory does not contain any DLLs. Only
> .h, .inl and .cpp files have been copied. Is this correct? Should I
> copy them by hand? Should I copy anything else by hand?
If you didn't provide any options, then this is what should be
expected. If you want to install DLL's in addition to all of the other
things that are installed by default, you need to run it using the
following:
MPC/prj_install.pl -a lib_output /c/ACE-5.6.5 .
Unfortunately, I just realized that this isn't clearly documented. The
script hasn't had much use (as far as I can tell).
HTH,
Chad
>
> Thanks a lot!
> -- Douglas
>
> */Chad Elliott /* wrote:
>
> Hi Douglas,
>
> Douglas Atique wrote:
Chad Elliott
> Hi again Chad,
> -a lib_output doesn't seem to have made any difference. After running
> prj_install as you say, I run
> find . -name "*.dll" and get nothing. Should I run something else with
> mwc.pl to get some ins file to be generated for the DLLs? Am I missing
> something else?
From which directory were you running? As a test, I ran the following
from $ACE_ROOT:
$MPC_ROOT/prj_install.pl -a lib_output ~/testing ace/ACE.ins
And it resulted in header files in ~/testing/ace and the ACE libs in
~/testing/lib.
>
> The default.features file worked ok, thanks. Now ACE_SSL doesn't get
> skipped anymore.
Good.
Thanks,
Chad
>
> Cheers,
> Doug
Douglas Atique
I ran the following:Many .h, .inl and .cpp files (I suppose all that should be installed) were copied to the install directory. However no .dll files were.
-- Doug
Chad Elliott <elli...@ociweb.com> wrote:
Douglas Atique wrote:
> Hi again Chad,
> -a lib_output doesn't seem to have made any difference. After running
> prj_install as you say, I run
> find . -name "*.dll" and get nothing. Should I run something else with
> mwc.pl to get some ins file to be generated for the DLLs? Am I missing
> something else?
From which directory were you running? As a test, I ran the following
from $ACE_ROOT:
$MPC_ROOT/prj_install.pl -a lib_output ~/testing ace/ACE.ins
And it resulted in header files in ~/testing/ace and the ACE libs in
~/testing/lib.
>
> The default.features file worked ok, thanks. Now ACE_SSL doesn't get
> skipped anymore.
Good.
Thanks,
Chad
>
> Cheers,
> Doug
>
Chad Elliott
> The current directory is $ACE_ROOT.
> I ran the following:
> MPC/prj_install.pl -a lib_output /c/ACE-5.6.5 .
> Many .h, .inl and .cpp files (I suppose all that should be installed)
> were copied to the install directory. However no .dll files were.
Hmm... Can you send me the ACE.ins from the ace directory and the ls -l
output from $ACE_ROOT/lib?
Thanks,
Chad
>
> -- Doug
J.T. Conklin
> Didn't work, configure says it is not usable.
> Will pursue further Chad's approach.
Hi Douglas,
Feel free to file a bugzilla issue with the attached config.log file.
It may be a relatively simple fix to get the autoconf build working
for mingw (or any other target where it currently fails).
--jtc
--
J.T. Conklin
Johnny Willemsen
> I haven't tried autoconf install for a while. Is it functional for mingw?
No, so far as I know it doesn't work.
Johnny Willemsen
Remedy IT
Postbus 101
2650 AC Berkel en Rodenrijs
The Netherlands
www.theaceorb.nl / www.remedy.nl
*** Integrated compile and test statistics see
http://scoreboard.theaceorb.nl ***
*** Commercial service and support for ACE/TAO/CIAO ***
*** Get your free TAO Programmers Guide copy from
http://www.theaceorb.nl ***
Chad Elliott
Douglas Atique wrote:
> Here they are. Interestingly, when I got your reply I noticed that
> ACE.ins didn't exist. So I removed the whole ACE_wrappers directory,
> unpacked it again from tarball, built it all and installed but the lib
> directory still doesn't get created.
> For reference, here is the command that generated
> install-dir-contents.txt.gz (run from $ACE_ROOT):
> MPC/prj_install.pl -a lib_output -a exe_output -a pkgconfig_files -a
> gperf_files -a build_files -a documentation_files /c/ACE-5.6.5 .
> I derived the tag names by grepping all .ins files for ":$" and picked
> the ones that seemed useful for generating a binary distribution.
Thanks for the files. I can now see why you're not getting any
libraries. I have never seen the output of MinGW and did not realize
that it named libraries libXXX.dll.
If you get the latest version of MPC from svn, it will work with your build.
svn co svn://svn.dre.vanderbilt.edu/DOC/MPC/trunk MPC
Thanks,
Chad
>
> -- Doug
>
> *//*
Johnny Willemsen
> > No, then it is not an option. It seems the ins files are tied to a
> real
> > generator, would it be possible to just run -gendir for TAO_ACE.mwc,
> that
> > would generate the install files for just the core libs/tools
> >
>
> Yes, if files are added dependent upon the project type then the .ins
> file will be tied to that project type. And yes, -genins for
> TAO_ACE.mwc would get just the core libs and tools.
What about a generic install generator, do we have files dependent on a real
projec type? It seems interesting to just get the ins files for the core
libs as part of the distribution.
Johnny
Chad Elliott
If it is decided to always generate them, I would choose to use the
gnuace project type. The .ins files generated with this project type
would work with all other project types.
As far as files specific to a project type, I don't know. I would have
to look through all of the mpc files for the core.
Chad
> Johnny
>
>
Johnny Willemsen
HI,
MinGW uses the Windows threading API, supporting that with autoconf doesn't seem a relative simple fix to me.
Johnny
From:
ace-user...@list.isis.vanderbilt.edu
[mailto:ace-user...@list.isis.vanderbilt.edu] On Behalf Of Douglas
Atique
Sent: Wednesday, May 21, 2008 3:09 PM
To: j...@acorntoolworks.com
Cc: ace-...@list.isis.vanderbilt.edu
Subject: Re: [ace-users] ACE install question
I have tried to create an account at the Vanderbilt bugzilla
site, but it says I don't have permission to file any bugs...
Thus I have attached my config.log here.
I hope that helps.
Cheers,
Doug
"J.T. Conklin" <j...@acorntoolworks.com> wrote:
J.T. Conklin
> MinGW uses the Windows threading API, supporting that with autoconf doesn't
> seem a relative simple fix to me.
Hi Johnny,
Yes, after seeing Douglas' config.log, supporting mingw with the
autoconf build seems much more difficult than I thought/hoped it
would be. It goes far beyond just threading.
The first thing that needs to be done is a change to ace/platform.m4
to ensure that ACE_WIN32 is defined. At that point, we'd have to do
another configure (which would surely fail); but as things are now,
there is just too much output in the config.log to know what changes
would be needed next.
I'll make the changes to platform.m4, but I suspect this will need
effort by someone with an true desire/need to get the autoconf build
working on mingw systems.
--jtc
--
J.T. Conklin
Johnny Willemsen
> Yes, after seeing Douglas' config.log, supporting mingw with the
> autoconf build seems much more difficult than I thought/hoped it
> would be. It goes far beyond just threading.
>
> The first thing that needs to be done is a change to ace/platform.m4
> to ensure that ACE_WIN32 is defined. At that point, we'd have to do
> another configure (which would surely fail); but as things are now,
> there is just too much output in the config.log to know what changes
> would be needed next.
>
> I'll make the changes to platform.m4, but I suspect this will need
> effort by someone with an true desire/need to get the autoconf build
> working on mingw systems.
Douglas, when JT has made the changes in the repo could you try a svn head
version? See the TAO Programmers guide at www.theaceorb.nl for how to obtain
the svn copy.
Johnny
Douglas Atique
Cheers,
Doug
J.T. Conklin
> Sure, I can try the SVN head version. Just let me know when I can
> get it. By the way, do I need to generate any build files with MPC
> for autoconf builds? Or is the configure script already there?
Hi Douglas,
I checked in the change to platforms.m4 I mentioned before. After you
check out the SVN head, you will need to regenerate the configure
script, Makefile.in's, etc. For that you will need autoconf,
automake, and libtool. With those installed, all you'll need
to do is "autoreconf -ivf" from the toplevel source directory.
Once you've done that, run the configure script again, and send me the
config.log when it fails :-). I'm willing to work with you as long as
it takes (and as long as you're willing) to get the autoconf/automake
infrastructure working with mingw.
--jtc
--
J.T. Conklin
Steve Huston
> Sure, I can try the SVN head version. Just let me know when I can
> get it.
It's there now.
> By the way, do I need to generate any build files with MPC for
> autoconf builds? Or is the configure script already there?
You need not generate anything with MPC, but you will need to run the
bootstrap script to generate the configure script. For this, you'll
need an up-to-date autoconf, automake, and libtool.
Thanks,
-Steve
--
Steve Huston, Riverace Corporation
Want to take ACE training on YOUR schedule?
See http://www.riverace.com/training.htm
Chad Elliott
> Hi Chad,
>
> While building a simple program with MinGW, I noticed that (at least) the
> following files are not getting copied by prj_install.pl:
> ace/config-win32-mingw.h
> ace/config-g++-common.h
> ace/Unbounded_Set_Ex.cpp
> ace/Unbounded_Set_Ex.h
> ace/Unbounded_Set_Ex.inl
>
> After copying them by hand to the install directory, the build succeeded. I
> thought you'd be interested in this information.
Thanks. It just means that they aren't listed in the ace.mpc file. I'll see
about adding them.
Chad
>
> -- Doug
>
> Chad Elliott <elli...@ociweb.com> wrote: Douglas Atique wrote:
> > That worked flawlessly. Thanks.
>
> Great. That's good to hear.
>
> Thanks,
> Chad
>
> > -- Doug
> >
> > */Chad Elliott /* wrote:
> >
> > Douglas Atique wrote:
> > > Hi Chad,
> > >
> > > I couldn't access the SVN repository. I guess the svn: port is
> > blocked
> > > from my corporate network. I also tried to access it as https:
> > but it
> > > asks for a username/password which I don't have. Do you think you
> > > could send me a tarball with the changes?
> >
> > No problem.
> >
> > >
> > > Alternatively, I was thinking of renaming every DLL in the
> > > ACE_wrappers/lib directory to remove the lib prefix, but that might
> > > not work, as some DLLs might depend on others and I think they
> > refer
> > > by name to their dependencies.
> >
> > Yeah, that doesn't sound like a good idea.
> >
> > Chad
> >
> > >
> > > Thanks,
> > > Doug
> > >
> > > */Chad Elliott /* wrote:
> > >