stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Farid Zaripov" <>
Subject RE: [PATCH] Scripts, generating solution and projects for MSVC/ICC [2]
Date Mon, 02 Oct 2006 14:24:03 GMT
> -----Original Message-----
> From: Martin Sebor [] 
> Sent: Saturday, September 30, 2006 1:43 AM
> To:
> Subject: Re: [PATCH] Scripts, generating solution and 
> projects for MSVC/ICC [2]
> Farid Zaripov wrote:
> >   Patch for scripts of Windows build infrastructure is here:
> >
> Btw., I noticed that the _RWBUILD_std macro is (still) being 
> #defined. It shouldn't be.
  The _RWBUILD_std macro used to define properly _RWSTD_EXPORT macro.

_defs.h, line 454:
// set up Win32/64 DLL export/import directives
// _DLL - defined by the compiler when either -MD or -MDd is used
// RWDLL - defined for all Rogue Wave(R) products built as shared libs
// _RWSHARED - defined for libstd built/used as a shared lib
#if (defined (_WIN32) || defined (_WIN64)) && \
    (defined (RWDLL)  || defined (_RWSHARED))

#  ifdef _RWBUILD_std
#    define _RWSTD_EXPORT            __declspec (dllexport)
#  else
#    define _RWSTD_EXPORT            __declspec (dllimport)
#  endif   // _RWBUILD_std

  Should we replace #ifdef _RWBUILD_std to #ifdef _RWSTD_LIB_SRC in

> Also, it would be good to document the variables defined in 
> the .config files. I have an idea what CPPFLAGS might be but 
> what's CONVERT or SLNVER (these are rhetorical questions)? 
> While on the subject of these variables, shouldn't -qnoipo be 
> defined in LDFLAGS rather than in LD?
  CXX, LD, AR variables are used at configure step only. The CPPFLAGS,
are used in libraries, examples and tests builds also. Thus LD variable
should contain 
additiona options for configure step. We can rename LDFLAGS to
LDFLAGS.wide and
add LDFLAGS.config=-qnoipo. BTW it seems to me -qnoipo flags is
unnecessary (I just
copied this flags from the previous scripts). All works fine without
this flag.

> And shouldn't we be using cl (or icl) to link instead of invoking the
linker directly?
  I not found where MS recommends invoke cl.exe instead of link.exe to
link files.


View raw message