adobe-source-devel

[Adobe-source-devel] expression_formatter.hpp failing to compile

[Robert D. <rcd...@gm...>]

Hey guys,
I'm compiling the HEAD in Perforce, and I'm running into a few compiler
errors on MSVC9:

D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(32)
: error C2504: 'basic_omanipulator' : base class undefined
D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(32)
: error C2143: syntax error : missing ',' before '<'
D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
: error C2143: syntax error : missing ';' before '<'
D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
: error C4430: missing type specifier - int assumed. Note: C++ does not
support default-int
D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
: error C2238: unexpected token(s) preceding ';'

These errors occurred while compiling property_model_formatter.cpp in APL.
Any reason for this failure? Are there certain files in APL that I should
NOT be compiling?

Re: [Adobe-source-devel] expression_formatter.hpp failing to compile

[Robert D. <rcd...@gm...>]

I have a feeling that I can't simply start blindly compiling APL. I presume
there are some prerequisites (Preprocessor definitions, etc) that I need to
obtain/setup. Is there a developer readme somewhere that I can reference?

On Tue, May 19, 2009 at 8:49 PM, Robert Dailey <rcd...@gm...> wrote:

> Hey guys,
> I'm compiling the HEAD in Perforce, and I'm running into a few compiler
> errors on MSVC9:
>
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(32)
> : error C2504: 'basic_omanipulator' : base class undefined
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(32)
> : error C2143: syntax error : missing ',' before '<'
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
> : error C2143: syntax error : missing ';' before '<'
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
> : error C4430: missing type specifier - int assumed. Note: C++ does not
> support default-int
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
> : error C2238: unexpected token(s) preceding ';'
>
> These errors occurred while compiling property_model_formatter.cpp in APL.
> Any reason for this failure? Are there certain files in APL that I should
> NOT be compiling?
>

Re: [Adobe-source-devel] expression_formatter.hpp failing to compile

[Mat M. <mat...@em...>]

On Tue, May 19, 2009 at 7:05 PM, Robert Dailey <rcd...@gm...> wrote:
> I have a feeling that I can't simply start blindly compiling APL. I presume
> there are some prerequisites (Preprocessor definitions, etc) that I need to
> obtain/setup. Is there a developer readme somewhere that I can reference?

One approach is to use bjam, the only fully supported build option at
present, for your first attempts. There is a somewhat dated
description of the build process here:

http://stlab.adobe.com/asl_readme.html#Building_Under_Win32

There is also an "ASL command window", resembling the "Visual Studio
Command Window", that can be of some assistance here. After initial
setup, building involves a matter of cd-ing to the appropriate
directory and invoking the command as:

  bjam

This builds the basic static debug version of all libraries (including
the relevant parts of boost), the apps, and runs the unit tests.
Variations are possible, given more interesting command lines (debug,
release, compiler, processor architecture, dll, etc.)

The command:

  bjam -n

won't actually build, but will show the commands that would be used,
together with all defined macros, etc.

I believe that IDE projects also offer a GUI for examining the full
set of build flags, but I recommend the bjam to begin with.

 - Mat

Re: [Adobe-source-devel] expression_formatter.hpp failing to compile

[Robert D. <rcd...@gm...>]

Thanks for the help.
I must be going crazy and seeing things, because this error:

expression_formatter.hpp(32) : error C2504: 'basic_omanipulator' : base
class undefined

shouldn't be happening.

expression_formatter.hpp includes <adobe/iomanip.hpp>, which in turn
includes
<adobe/manip.hpp>, which contains the definition of
basic_omanipulator. I checked my include paths, and I have
adobe_source_libraries and adobe_platform_libraries set in my include
path. And it obviously has no problem finding the files it is
including.

Any explanation for this, other than the fact that I'm not using bjam?
I think that regardless of what build system I'm using, this error
should not be occurring.

On Tue, May 19, 2009 at 11:07 PM, Mat Marcus <mat...@em...> wrote:

> On Tue, May 19, 2009 at 7:05 PM, Robert Dailey <rcd...@gm...> wrote:
> > I have a feeling that I can't simply start blindly compiling APL. I
> presume
> > there are some prerequisites (Preprocessor definitions, etc) that I need
> to
> > obtain/setup. Is there a developer readme somewhere that I can reference?
>
> One approach is to use bjam, the only fully supported build option at
> present, for your first attempts. There is a somewhat dated
> description of the build process here:
>
> http://stlab.adobe.com/asl_readme.html#Building_Under_Win32
>
> There is also an "ASL command window", resembling the "Visual Studio
> Command Window", that can be of some assistance here. After initial
> setup, building involves a matter of cd-ing to the appropriate
> directory and invoking the command as:
>
>  bjam
>
> This builds the basic static debug version of all libraries (including
> the relevant parts of boost), the apps, and runs the unit tests.
> Variations are possible, given more interesting command lines (debug,
> release, compiler, processor architecture, dll, etc.)
>
> The command:
>
>  bjam -n
>
> won't actually build, but will show the commands that would be used,
> together with all defined macros, etc.
>
> I believe that IDE projects also offer a GUI for examining the full
> set of build flags, but I recommend the bjam to begin with.
>
>  - Mat
>

Re: [Adobe-source-devel] expression_formatter.hpp failing to compile

[Mat M. <mat...@em...>]

On Tue, May 19, 2009 at 9:15 PM, Robert Dailey <rcd...@gm...> wrote:
> Thanks for the help.
> I must be going crazy and seeing things, because this error:
> expression_formatter.hpp(32) : error C2504: 'basic_omanipulator' : base
> class undefined
> shouldn't be happening.
> expression_formatter.hpp includes <adobe/iomanip.hpp>, which in turn
> includes
> <adobe/manip.hpp>, which contains the definition of basic_omanipulator. I checked my include paths, and I have adobe_source_libraries and adobe_platform_libraries set in my include path. And it obviously has no problem finding the files it is including.
> Any explanation for this, other than the fact that I'm not using bjam? I think that regardless of what build system I'm using, this error should not be occurring.


I'd need a bit more info before I can answer usefully. Are you
compiling the Adobe Begin visual studio solution, or is this your own
project, or are you using CMake? If you are not using one of the
provided bjam files or visual studio solutions then you may not have
the necessary flags, options and macros set. The reasons that I
encouraged you to begin with bjam included:
  1) Once things were configured you'd have a baseline build that you
could compare to/test against.
  2) You could use the build system as an oracle to determine the
options to pass the compiler if you're going your own way

 - Mat

Re: [Adobe-source-devel] expression_formatter.hpp failing to compile

[Robert D. <rcd...@gm...>]

On Tue, May 19, 2009 at 11:44 PM, Mat Marcus <mat...@em...> wrote:

> I'd need a bit more info before I can answer usefully. Are you
> compiling the Adobe Begin visual studio solution, or is this your own
> project, or are you using CMake? If you are not using one of the
> provided bjam files or visual studio solutions then you may not have
> the necessary flags, options and macros set. The reasons that I
> encouraged you to begin with bjam included:
>  1) Once things were configured you'd have a baseline build that you
> could compare to/test against.
>  2) You could use the build system as an oracle to determine the
> options to pass the compiler if you're going your own way


I'm compiling every single source file under:
adobe_platform_libraries/adobe/.....
adobe_platform_libraries/windows/adobe/....

These are being compiled as a single library.

I looked at <adobe/iomanip.hpp>, <adobe/manip.hpp>, and
expression_formatter.hpp. I did not see any preprocessor conditions, nor
anything else that made it immediately obvious that a certain command line
configuration must be present in order for this to successfully compile.

When I get home, I will reference the bjam scripts to see if I can't hunt
down the problem and I'll also try to compile it using bjam. Please note,
however, that I do not know
bjam nor do I have a desire to learn it. I was hoping I could resolve
this issue without depending on bjam too much. For example, if there
were documentation somewhere that adequately explained
how to build APL and ASL. For example, I would expect such documentation to
inform me of:

   - All of the command line options required to successfully build both APL
   and ASL.
   - All of the files that are compiled per-platform. Currently, for ASL, I
   am compiling every single CPP file I can find in that directory tree
   (adobe_source_libraries). For APL, it's a bit trickier, since there are
   platform specific files in there.
   - Any preprocessor definitions that are required by both APL and ASL.
   - Anything else out of the ordinary.

I have yet to read the URL you linked me to earlier, so some of these may be
addressed there. However, from what you've told me so far, there seems to be
a high dependency on bjam to figure out how to properly build the project.

Re: [Adobe-source-devel] expression_formatter.hpp failing to compile

[Sean P. <sea...@ma...>]

What cpp file was being compiled?

Sean

On May 19, 2009, at 6:49 PM, Robert Dailey wrote:

> Hey guys,
>
> I'm compiling the HEAD in Perforce, and I'm running into a few  
> compiler errors on MSVC9:
>
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(32) : error C2504: 'basic_omanipulator' :  
> base class undefined
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(32) : error C2143: syntax error : missing  
> ',' before '<'
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(34) : error C2143: syntax error : missing  
> ';' before '<'
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(34) : error C4430: missing type specifier -  
> int assumed. Note: C++ does not support default-int
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(34) : error C2238: unexpected token(s)  
> preceding ';'
>
> These errors occurred while compiling property_model_formatter.cpp  
> in APL. Any reason for this failure? Are there certain files in APL  
> that I should NOT be compiling?
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables
> unlimited royalty-free distribution of the report engine
> for externally facing server and web deployment.
> http://p.sf.net/sfu/businessobjects_______________________________________________
> Adobe-source-devel mailing list
> Ado...@li...
> https://lists.sourceforge.net/lists/listinfo/adobe-source-devel

Re: [Adobe-source-devel] expression_formatter.hpp failing to compile

[Sean P. <sea...@ma...>]

The issue may be that ADOBE_STD_SERIALIZATION=1 is not defined (this  
should be an optional flag but we may not fully be testing without  
it). Also note that boost and TBB have configuration options (well  
documented) that need to be set appropriately.

Looking at my GCC build I see the following:

ADOBE_STD_SERIALIZATION=1
BOOST_SIGNALS_STATIC_LINK=1 BOOST_THREAD_USE_LIB=1 BOOST_ALL_NO_LIB=1
__TBB_NO_IMPLICIT_LINKAGE=1


Sean

On May 19, 2009, at 6:49 PM, Robert Dailey wrote:

> Hey guys,
>
> I'm compiling the HEAD in Perforce, and I'm running into a few  
> compiler errors on MSVC9:
>
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(32) : error C2504: 'basic_omanipulator' :  
> base class undefined
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(32) : error C2143: syntax error : missing  
> ',' before '<'
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(34) : error C2143: syntax error : missing  
> ';' before '<'
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(34) : error C4430: missing type specifier -  
> int assumed. Note: C++ does not support default-int
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(34) : error C2238: unexpected token(s)  
> preceding ';'
>
> These errors occurred while compiling property_model_formatter.cpp  
> in APL. Any reason for this failure? Are there certain files in APL  
> that I should NOT be compiling?
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables
> unlimited royalty-free distribution of the report engine
> for externally facing server and web deployment.
> http://p.sf.net/sfu/businessobjects_______________________________________________
> Adobe-source-devel mailing list
> Ado...@li...
> https://lists.sourceforge.net/lists/listinfo/adobe-source-devel

Re: [Adobe-source-devel] expression_formatter.hpp failing to compile

[Robert D. <rcd...@gm...>]

With everyone's help here, along with a little bit of peeking into bjam
script files, I managed to generate the following list of preprocessor
defines that I am specifying for both ASL and APL on Windows when I build
them:
   _UNICODE
   UNICODE
   _SCL_SECURE_NO_DEPRECATE
   _CRT_SECURE_NO_DEPRECATE
   USE_WINTHREAD
   _WIN32_WINNT=0x0501
   ADOBE_TEST_MICROSOFT_NO_DEPRECATE
   ADOBE_SERIALIZATION
   ADOBE_STD_SERIALIZATION
   BOOST_SIGNALS_STATIC_LINK
   BOOST_THREAD_USE_LIB
   BOOST_ALL_NO_LIB
   __TBB_NO_IMPLICIT_LINKAGE
   NOMINMAX

Everything seems to be working fine now! So far, I've been able to compile
APL and ASL into static libraries on Windows using CMake. However, the real
test will be getting the Begin test app to work! Thanks for the support
everyone.


On Wed, May 20, 2009 at 1:51 PM, Sean Parent <sea...@ma...> wrote:

> The issue may be that ADOBE_STD_SERIALIZATION=1 is not defined (this should
> be an optional flag but we may not fully be testing without it). Also note
> that boost and TBB have configuration options (well documented) that need to
> be set appropriately.
>
> Looking at my GCC build I see the following:
>
> ADOBE_STD_SERIALIZATION=1
> BOOST_SIGNALS_STATIC_LINK=1 BOOST_THREAD_USE_LIB=1 BOOST_ALL_NO_LIB=1
> __TBB_NO_IMPLICIT_LINKAGE=1
>
>
> Sean
>
> On May 19, 2009, at 6:49 PM, Robert Dailey wrote:
>
>  Hey guys,
>>
>> I'm compiling the HEAD in Perforce, and I'm running into a few compiler
>> errors on MSVC9:
>>
>> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(32)
>> : error C2504: 'basic_omanipulator' : base class undefined
>> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(32)
>> : error C2143: syntax error : missing ',' before '<'
>> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
>> : error C2143: syntax error : missing ';' before '<'
>> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
>> : error C4430: missing type specifier - int assumed. Note: C++ does not
>> support default-int
>> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
>> : error C2238: unexpected token(s) preceding ';'
>>
>> These errors occurred while compiling property_model_formatter.cpp in APL.
>> Any reason for this failure? Are there certain files in APL that I should
>> NOT be compiling?
>>
>> ------------------------------------------------------------------------------
>> Crystal Reports - New Free Runtime and 30 Day Trial
>> Check out the new simplified licensing option that enables
>> unlimited royalty-free distribution of the report engine
>> for externally facing server and web deployment.
>>
>> http://p.sf.net/sfu/businessobjects_______________________________________________
>> Adobe-source-devel mailing list
>> Ado...@li...
>> https://lists.sourceforge.net/lists/listinfo/adobe-source-devel
>>
>
>