Difference: AthenaStuff (1 vs. 20)

Revision 202006-12-20 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"
Deleted:
<
<
 

Revision 192006-10-31 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"
Added:
>
>
 

Revision 182006-03-31 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"
Added:
>
>
  DONT BELIEVE ANYTHING BELOW!

Revision 172006-03-29 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"
Changed:
<
<
DONT BELIEVE ANYTHING YOU READ ON THIS PAGE!
>
>

DONT BELIEVE ANYTHING BELOW!

  INFO MIGHT BE TRUE BUT IT IS ALSO VERY OUTDATED!

Revision 162006-03-22 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"
Added:
>
>
DONT BELIEVE ANYTHING YOU READ ON THIS PAGE!

INFO MIGHT BE TRUE BUT IT IS ALSO VERY OUTDATED!

 

From Generation to Analysis (more or less)

Revision 152005-05-23 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"

From Generation to Analysis (more or less)

Line: 16 to 16
 
  • MuOns in ESD and AOD (from 9.4.0 on)

Miscellaneous

Added:
>
>

 

Revision 142005-05-23 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"

From Generation to Analysis (more or less)

Line: 15 to 15
 

Miscellaneous

Added:
>
>
 

Revision 132005-05-10 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"

From Generation to Analysis (more or less)

Line: 9 to 9
 
Added:
>
>
 

Content of ESD and AOD

Revision 122005-04-22 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"

From Generation to Analysis (more or less)

Line: 23 to 23
 
Added:
>
>
  -- DerSchrecklicheSven - 22 Jul 2004

Revision 112005-04-16 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"

From Generation to Analysis (more or less)

Line: 8 to 8
 
Added:
>
>
 

Content of ESD and AOD

Revision 102005-03-18 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"

From Generation to Analysis (more or less)

Line: 21 to 21
 
Added:
>
>
  -- DerSchrecklicheSven - 22 Jul 2004

Revision 92005-02-10 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"

From Generation to Analysis (more or less)

Line: 11 to 11
 

Content of ESD and AOD

Added:
>
>
  • MuOns in ESD and AOD (from 9.4.0 on)
 

Miscellaneous

Revision 82005-01-12 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"

From Generation to Analysis (more or less)

Line: 12 to 12
 

Miscellaneous

Added:
>
>
 

Revision 72004-12-15 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"

From Generation to Analysis (more or less)

Line: 12 to 12
 

Miscellaneous

Changed:
<
<
>
>
 

Revision 62004-12-01 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"

From Generation to Analysis (more or less)

Changed:
<
<
>
>
 
Added:
>
>

Content of ESD and AOD

 

Miscellaneous

Added:
>
>
 
Changed:
<
<
>
>
  • Setting CompilerFlags via requirements files
  • getting more info on MySQL server error numbers
  -- DerSchrecklicheSven - 22 Jul 2004

Revision 52004-11-16 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"
Added:
>
>

From Generation to Analysis (more or less)

Miscellaneous

 
Changed:
<
<

  • Setting compiler flags via requirements files:
If you want one package to compile in dbg (but the rest in opt) add

macro_append (right macro) " -g"

for -g it would be:

macro_append cppflags " -g"

to your requirements file.

If you want the O2 flag removed (or any other) add

macro_remove (right macro) " -O2"

to your requirements file.

To find out which macro a flag is in read through the mail by RD:


Hi Andreas,

macro_remove works. The question is to find which macro.

From any makefile, e.g. .make you'll see that the compile command is cppcomp

% cmt show macro cppcomp

# Package CMT v1r16p20040701 defines macro cppcomp as '$(cpp) -c $(includes) $(cppdebugflags) $(cppflags) $(pp_cppflags)' for default tag # # Selection :

cppcomp='$(cpp) -c $(includes) $(cppdebugflags) $(cppflags) $(pp_cppflags)'

so it is one of the above macros, not necessarily cppflags.

Apparently it is in cppdebugflags:

% cmt show macro cppdebugflags

# Package

GaudiPolicy
v5r15p1 defines macro cppdebugflags as '$(cppoptimized_s)' for tag 'optimized' # # Selection : cppdebugflags='$(cppoptimized_s)'

% cmt show macro_value cppdebugflags -O2

see you, RD


Hi

RD is right to say that the "The question is to find which macro"

To complete this info, generally to obtain this information you can do :

> cmt show macros | grep "O2"

This should give you something like:

> cmt show macros | grep O2
cppoptimized_s='-O2' foptimized_s='-O2'

Telling you that either cppoptimized_s or foptimized_s is providing this option [according to whether you are using C++ or Fortran]

Then of course you can obtain more details about this macro (especially WHO defines it):

> cmt show macro cppoptimized_s
# Package GaudiPolicy v5r15p1 defines macro cppoptimized_s as '-O2' for default tag # # Selection : cppoptimized_s='-O2'

Then you may freely modify the definition of this macro in you package using a macro_remove, a macro_append, a macro_prepend, etc...

Remember also that if the modification is done privately it won't influence your client packages

=================================== private macro_remove cppoptimized_s '-O2' ===================================

while if made in a public section of your package, the mod will affect all client packages.

You can also figure out how this macro is effectively used:

> cmt show macros | grep '$.cppoptimized_s'
cppdebugflags='$(cppoptimized_s)'

% cmt show macros | grep '$.cppdebugflags' cppcomp='$(cpp) -c $(includes) $(cppdebugflags) $(cppflags) $(pp_cppflags)'

% cmt show macros | grep '$.cppcomp'

Here cppcomp is directly used in the make fragment generated by CMT

% grep cppcomp $CMTROOT/fragments/* .../cpp: ... .../cpp_library: ...

Cheers Christian.

>
>
  -- DerSchrecklicheSven - 22 Jul 2004
Added:
>
>

Revision 42004-07-28 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"
Added:
>
>

 
  • Setting compiler flags via requirements files:
If you want one package to compile in dbg (but the rest in opt) add

Revision 32004-07-26 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"
  • Setting compiler flags via requirements files:
If you want one package to compile in dbg (but the rest in opt) add
Line: 52 to 55
 -O2

see you, RD

Added:
>
>

Hi

RD is right to say that the "The question is to find which macro"

To complete this info, generally to obtain this information you can do :

> cmt show macros | grep "O2"

This should give you something like:

> cmt show macros | grep O2
cppoptimized_s='-O2' foptimized_s='-O2'

Telling you that either cppoptimized_s or foptimized_s is providing this option [according to whether you are using C++ or Fortran]

Then of course you can obtain more details about this macro (especially WHO defines it):

> cmt show macro cppoptimized_s
# Package GaudiPolicy v5r15p1 defines macro cppoptimized_s as '-O2' for default tag # # Selection : cppoptimized_s='-O2'

Then you may freely modify the definition of this macro in you package using a macro_remove, a macro_append, a macro_prepend, etc...

Remember also that if the modification is done privately it won't influence your client packages

=================================== private macro_remove cppoptimized_s '-O2' ===================================

while if made in a public section of your package, the mod will affect all client packages.

You can also figure out how this macro is effectively used:

> cmt show macros | grep '$.cppoptimized_s'
cppdebugflags='$(cppoptimized_s)'

% cmt show macros | grep '$.cppdebugflags' cppcomp='$(cpp) -c $(includes) $(cppdebugflags) $(cppflags) $(pp_cppflags)'

% cmt show macros | grep '$.cppcomp'

Here cppcomp is directly used in the make fragment generated by CMT

% grep cppcomp $CMTROOT/fragments/* .../cpp: ... .../cpp_library: ...

 
Added:
>
>
Cheers Christian.
  -- DerSchrecklicheSven - 22 Jul 2004

Revision 22004-07-26 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="DerSchrecklicheSven"
Changed:
<
<
  • Compiling:
>
>
  • Setting compiler flags via requirements files:
 If you want one package to compile in dbg (but the rest in opt) add
Added:
>
>
macro_append (right macro) " -g"

for -g it would be:

 macro_append cppflags " -g"

to your requirements file.

If you want the O2 flag removed (or any other) add

Changed:
<
<
macro_remove cppflags " -O2"
>
>
macro_remove (right macro) " -O2"
  to your requirements file.
Added:
>
>
To find out which macro a flag is in read through the mail by RD:
Hi Andreas,

macro_remove works. The question is to find which macro.

From any makefile, e.g. .make you'll see that the compile command is cppcomp

% cmt show macro cppcomp # Package CMT v1r16p20040701 defines macro cppcomp as '$(cpp) -c $(includes) $(cppdebugflags) $(cppflags) $(pp_cppflags)' for default tag # # Selection : cppcomp='$(cpp) -c $(includes) $(cppdebugflags) $(cppflags) $(pp_cppflags)'

so it is one of the above macros, not necessarily cppflags.

Apparently it is in cppdebugflags:

% cmt show macro cppdebugflags # Package

GaudiPolicy
v5r15p1 defines macro cppdebugflags as '$(cppoptimized_s)' for tag 'optimized' # # Selection : cppdebugflags='$(cppoptimized_s)'

% cmt show macro_value cppdebugflags -O2

see you, RD

 -- DerSchrecklicheSven - 22 Jul 2004

Revision 12004-07-22 - AndreasWildauer

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="DerSchrecklicheSven"
  • Compiling:
If you want one package to compile in dbg (but the rest in opt) add

macro_append cppflags " -g"

to your requirements file.

If you want the O2 flag removed (or any other) add

macro_remove cppflags " -O2"

to your requirements file.

-- DerSchrecklicheSven - 22 Jul 2004

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback