Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
internal:abi [2016/10/30 17:53] – port the rest of the page temadownload:details:sbi [2016/11/18 16:03] (current) – ↷ Page moved and renamed from internal:abi to download:details:sbi sbs
Line 130: Line 130:
 ===== Search ===== ===== Search =====
  
 +<callout type="info" icon="true">
 +=== Alert: Be aware ===
 +
 +Needs re-writing by Hans or Artem!
 +
 +</callout>
 We distinguish between: We distinguish between:
  
Line 183: Line 189:
  
   - basic targets that define a combination of TARGET_ENV and basis-SBI. For example, we have:<code>   - basic targets that define a combination of TARGET_ENV and basis-SBI. For example, we have:<code>
-    target default_sbi: +target default_sbi: 
-    TARGET_ENV       :=  "host" +TARGET_ENV       :=  "host" 
-    SBI              :=  "seq" +SBI              :=  "seq" 
-    MT_MODE          :=  0 +MT_MODE          :=  0 
-    BACKEND          :=  "C99" +BACKEND          :=  "C99" 
-    RC_METHOD        :=  "local" +RC_METHOD        :=  "local" 
-    ...+...
  
-    target default_mt :: default_sbi: +target default_mt :: default_sbi: 
-    SBI              := "mt" +SBI              := "mt" 
-    MT_MODE          :=  1 +MT_MODE          :=  1 
-    USE_PHM_API      :=  1+USE_PHM_API      :=  1
  
-    target omp :: default_sbi: +target omp :: default_sbi: 
-    SBI              := "omp" +SBI              := "omp" 
-    BACKEND          := "omp" +BACKEND          := "omp" 
-    MT_MODE          :=  2 +MT_MODE          :=  2 
-    MT_LIB           := "omp" +MT_LIB           := "omp" 
-    CFLAGS           += " " +CFLAGS           += " " 
-    LDFLAGS          += " "+LDFLAGS          += " "
 </code> </code>
   - modifier targets that define properties or variants that are mainly orthorgonal to the basic targets. These targets do not inherit from any basic targets. Examples are: <code>   - modifier targets that define properties or variants that are mainly orthorgonal to the basic targets. These targets do not inherit from any basic targets. Examples are: <code>
-    target add_pth: +target add_pth: 
-    LIBS             +=  " -D_THREAD_SAFE -pthread " +LIBS             +=  " -D_THREAD_SAFE -pthread " 
-    CFLAGS           +=  " -D_THREAD_SAFE -pthread" +CFLAGS           +=  " -D_THREAD_SAFE -pthread" 
-    SBI              +=  "-pth" +SBI              +=  "-pth" 
-    MT_LIB           :=  "pthread"+MT_LIB           :=  "pthread"
  
-    target add_lpel: +target add_lpel: 
-    SBI              +=  "-lpel" +SBI              +=  "-lpel" 
-    MT_LIB           :=  "lpel" +MT_LIB           :=  "lpel" 
-    CFLAGS           +=  " " +CFLAGS           +=  " " 
-    LIBS             :=  "  -llpel " +LIBS             :=  "  -llpel " 
-    RC_METHOD        :=  "local_pasync_norc_desc"+RC_METHOD        :=  "local_pasync_norc_desc"
  
  
-    target add_rt: +target add_rt: 
-    SBI              +=  "-rtspec" +SBI              +=  "-rtspec" 
-    RTSPEC           :=  1+RTSPEC           :=  1
 </code> </code>
   - pre-defined final targets that are often-used combinations of one basic target with a set of modifier targets. These should be defined by means of inheritance only. Examples are: <code>   - pre-defined final targets that are often-used combinations of one basic target with a set of modifier targets. These should be defined by means of inheritance only. Examples are: <code>
-    target seq :: default_sbi:+target seq :: default_sbi:
  
-    target mt_pth :: default_mt :: add_pth:+target mt_pth :: default_mt :: add_pth:
  
-    target mt_pth_rt :: mt_pth :: add_rt:+target mt_pth_rt :: mt_pth :: add_rt:
  
-    target mt_lpel :: default_mt :: add_lpel:+target mt_lpel :: default_mt :: add_lpel:
 </code> </code>
  
-For better maintainability of the developer version, the monolithic sac2crc file is split up into several files that contain logically coherent sets of targets. All these can be found in the setup directory. They are being combined via autoconf/configure through the file ''sac2crc.pre.in'' in that very directory. +For better maintainability of the developer version, the monolithic ''sac2crc'' file is split up into several files that contain logically coherent sets of targets. All these can be found in the setup directory. They are being combined via autoconf/configure through the file ''sac2crc.pre.in'' in that very directory.