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
>