Flex SDK bin命令解析–mxmlc参数列表

Flex编译器以及常用编译参数分类：待分类2011-07-13 16:20 39人阅读评论(0) 收藏举报常见Flex编译器参数汇总verbose-stacktraces此Flex编译器参数指定SWF在运行时异常信息中包含行号和文件名，这将使产生的SWF文件更大些，带verbose-stacktraces的SWF还是和调试版本的SWF有区别的。

source-pathpath-element添加其他源代码目录或文件，可以使用通配符来添加目录中所有文件或子目录，也可使用+=在默认路径上来追加新参数，例如-source-path+=/Users/base/Projectinclude-libraries此Flex编译器参数指定SWF文件被编译到程序中并链接库中所有类和资源到SWF上。

如果你的程序需要加载其他模块这个参数就很有用了。

library-path跟include-libraries选项类似，但是只引用类和资源以供SWF使用，这样可保持SWF文件的可管理性。

locale此Flex编译器参数指定SWF文件的区域属性，例如使用-locale=es_ES指定SWF区域为西班牙use-network此Flex编译器参数指示SWF是否可以访问网络服务或者应用标准的FlashPlayer权限策略。

例如-usenetwork=false指定SWF有本地文件系统访问权但不能访问任何网络服务，默认为trueframes.frame启动应用程序资源代理流，然后通过ModuleManager类公布其接口，在特殊情况下，比如在代码中已经引入资源但是并不需要移动资源到外部SWF文件，这时此参数可使应用程序启动时间大大减少，这是一个很复杂但很有用的参数。

keep-all-type-selectors保证所有样式信息都被编译进SWF，甚至是程序没有用到的。

这点非常重要，因为有可能程序加载的其他组件需要这些样式信息。

默认值为false，也就是说没有用到的样式信息不会被编译进SWF。

MXML 语法MXML 是Adobe Flex™应用中一种用于展示用户界面组件的XML 语言。

主题∙MXML基本语法∙设置组件属性MXML 基本语法大多数MXML标签相当于ActionScript 3.0的类或者类属性。

Flex解析MXML标签，并将其编译成一个包含对应ActionScript对象的SWF文件。

ActionScript 3.0 使用的语法基于 ECMAScript语言规范草案（第4版）。

ActionScript 3.0 包含下列特性：∙正式的类定义语法∙正式的包结构∙键入变量、参数和返回值（仅在编译期）∙隐含的getter和setter，使用get和set关键字∙继承∙公共和私有成员∙静态成员∙类型转换符关于ActionScript 3.0的更多信息，参见Using ActionScript。

MXML文件命名MXML文件名必须遵守下列命名约定：∙文件名必须是有效的ActionScript标识符，这意味着必须以字母或下划线（_）开头，其后只能包含字母、数字和下划线。

∙文件名不能和ActionScript类名、组件id值相同，或者单词是application。

不要使用和mx命名空间中MXML 标签名相匹配的文件名。

∙文件名必须以小写字母.mxml作为文件后缀。

表示ActionScript 类的标签使用对应于ActionScript类的MXML标签采用的命名约定和ActionScript类相同。

类名以大写字母开头，大写字母区分类名中的单词。

比如，当一个标签对应一个ActionScript类时，它的属性对应于该类的属性和事件。

设置组件属性MXML中组件属性使用的命名约定和对应的ActionScript属性相同。

属性名以小写字母开头，大写字母区分属性名中的单词。

大多数组件属性设置和标签属性一样，形式如下：<mx:Label width="50" height="25" text="Hello World"/>所有组件属性可以设置为子标签，形式如下：<mx:Label> <mx:width>50</mx:width> <mx:height>25</mx:height> <mx:text>Hello World</mx:text> </mx:Label>当设置属性值为一个复杂的Object时，通常可以使用子标签，因为不能指定一个复杂的Object作为标签属性值。

FLEX 中文手册这是flex手册的部分中文翻译，仅供参考•一些简单的例子•输入文件的格式•模式•如何匹配输入•动作•生成的扫描器•开始条件•文件结尾规则•与yacc一起使用一些简单的例子首先给出一些简单的例子，来了解一下如何使用flex。

下面的flex输入所定义的扫描器，用来将所有的“username”字符串替换为用户的登陆名字：%% username printf("%s", getlogin());默认情况下，flex扫描器无法匹配的所有文本将被复制到输出，所以该扫描器的实际效果是将输入文件复制到输出，并对每一个“username”进行展开。

在这个例子中，只有一个规则。

“username”是模式（pattern），“printf”是动作（action）。

“%%”标志着规则的开始。

这里是另一个简单的例子：int num_lines = 0, num_chars = 0;%% \n ++num_lines; ++num_chars; . ++num_chars;%% int main(void){yylex();printf("# of lines = %d, # of chars = %d\n", num_lines, num_chars);}该扫描器计算输入的字符个数和行数（除了最后的计数报告，并未产生其它输出）。

第一行声明了两个全局变量，“num_lines”和“num_chars”，可以在yylex()函数中和第二个“%%”后面声明的main()函数中使用。

有两个规则，一个是匹配换行符（“\n”）并增加行数和字符数，另一个是匹配所有不是换行符的其它字符（由正规表达式“.”表示）。

一个稍微复杂点的例子：/* scanner for a toy Pascal-like language */%{/* need this for the call to atof() below */#include <math.h>%}DIGIT [0-9] ID [a-z][a-z0-9]*%%{DIGIT}+ {printf( "An integer: %s (%d)\n", yytext,atoi( yytext ) );}{DIGIT}+"."{DIGIT}* {printf( "A float: %s (%g)\n", yytext,atof( yytext ) );}if|then|begin|end|procedure|function {printf( "A keyword: %s\n", yytext );}{ID} printf( "An identifier: %s\n", yytext );"+"|"-"|"*"|"/" printf( "An operator: %s\n", yytext );"{"[^}\n]*"}" /* eat up one-line comments */[ \t\n]+ /* eat up whitespace */. printf( "Unrecognized character: %s\n", yytext );%%int main(int argc, char **argv){++argv, --argc; /* skip over program name */if ( argc > 0 )yyin = fopen( argv[0], "r" );elseyyin = stdin;yylex();}这是一个类似Pascal语言的简单扫描器的初始部分，用来识别不同类型的标志（tokens）并给出报告。

编译MXML为SWF文件你将你的应用作为SWF文件部署，或者你如果有 Adobe LiveCycle Data Services ES你可以将你的应用作为一组MXML,as文件来部署。

如果你使用flex builder，你可以在flex builder中编译，运行swf文件，如果你的程序执行正确，你可以用copy这些文件到一个web容器中的方法，来部署这个应用。

用户可以通过http://hostname/path/filename.html访问这个已经部署的swf文件。

flex还有一个基于命令行的编译器，mxmlc，使用它你可以编译mxml文件，你可以使用mxmlc编译一个hello.mxml文件，例如：mxmlc --show-actionscript-warnings=true --strict=true c:/appDir/hello.mxml在这个例子中flexInstallDir 是flex的安装目录，appDir 是hello.mxml所在的文件夹。

编译的结果swf文件也就是hello.swf文件和hello.mxml在同一文件架下。

mxml标签和actionscript类的关系adobe用actionscript类库来实现flex,这个类库包含组件（容器和控件），管理类，数据服务类，和其他各种各样的类。

你可以使用mxml和actionscript语言和这些类库来开发你的应用。

mxml标签与actionscript类及类的属性保持一致，flex解析mxml标签，将其编译成一个swf文件，这个编译好的swf 文件中就有mxml文件对应的actionscript对象。

例如flex提供了actionscript的button类，这个类定义了flex的button控件，你在mxml中，可以这样创建一个button控件<mx:Button label="Submit"/>当你使用mxml标签声明一个控件的时候，你创建了一个这个空间类的实例。

Proprietary Flex SDK 3.4.0.0 GAGecko SDK Suite 4.1June 8, 2022 ArrayThe Proprietary Flex SDK is a complete software development suite for proprietary wire-less applications.Per its namesake, Flex offers two implementation options.The first uses Silicon Labs RAIL (Radio Abstraction Interface Layer), an intuitive and eas-ily-customizable radio interface layer designed to support both proprietary and standards-based wireless protocols.The second uses Silicon Labs Connect, an IEEE 802.15.4-based networking stack de-signed for customizable broad-based proprietary wireless networking solutions that re-quire low power consumption and operates in either the sub-GHz or 2.4 GHz frequencybands. The solution is targeted towards simple network topologies.The Flex SDK is supplied with extensive documentation and sample applications. All ex-amples are provided in source code within the Flex SDK sample applications.These release notes cover SDK version(s):3.4.0.0 GA released June 8, 2022Compatibility and Use NoticesFor information aboutsecurity updates and notices, see the Security chapter of the Gecko Platform Release notes installed with this SDK or on the TECH DOCS tab on https:///developers/flex-sdk-connect-networking-stack. Silicon Labs also strongly recommends that you subscribe to Security Advisories for up-to-date information. For instructions, or if you are new to the Silicon Labs Flex SDK, see Using This Release.Compatible Compilers:IAR Embedded Workbench for ARM (IAR-EWARM) version 9.20.4•Using wine to build with the IarBuild.exe command line utility or IAR Embedded Workbench GUI on macOS or Linux could result in incorrect files being used due to collisions in wine’s hashing algorithm for generating short file names.•Customers on macOS or Linux are advised not to build with IAR outside of Simplicity Studio. Customers who do should carefully verify that the correct files are being used.GCC (The GNU Compiler Collection) version 10.3-2021.10, provided with Simplicity Studio.Contents Contents1Connect Applications (1)1.1New Items (1)1.2Improvements (1)1.3Fixed Issues (1)1.4Known Issues in the Current Release (1)1.5Deprecated Items (1)1.6Removed Items (1)2Connect Stack (2)2.1New Items (2)2.2Improvements (2)2.3Fixed Issues (2)2.4Known Issues in the Current Release (2)2.5Deprecated Items (2)2.6Removed Items (2)3RAIL Applications (3)3.1New Items (3)3.2Improvements (3)3.3Fixed Issues (3)3.4Known Issues in the Current Release (3)3.5Deprecated Items (3)3.6Removed Items (3)4RAIL Library (4)4.1New Items (4)4.2Improvements (4)4.3Fixed Issues (4)4.4Known Issues in the Current Release (5)4.5Deprecated Items (5)4.6Removed Items (5)5Using This Release (6)5.1Installation and Use (6)5.2Security Information (6)5.3Support (7)Connect Applications 1 Connect Applications1.1 New ItemsAdded in release 3.4.0.0•PSA Crypto API usage•Major update of Connect - SoC ECDH Key Exchange1.2 ImprovementsNone1.3 Fixed IssuesNone1.4 Known Issues in the Current ReleaseIssues in bold were added since the previous release. If you have missed a release, recent release notes are available on the TECH DOCS tab on https:///developers/flex-sdk-connect-networking-stack.652925 EFR32XG21 is not supported for “Flex (Connect) - SoC LightExample DMP” and “Flex (Connect) - SoC Switch Example”1.5 Deprecated ItemsNone1.6 Removed ItemsNoneConnect Stack 2 Connect Stack2.1 New ItemsAdded in release 3.4.0.0•All of the crypto operations are now made through ARM PSA Crypo API, enabling the storage of the network security key in the Secure Vault.•Added a new API emberSetPsaSecurityKey() that indicates which PSA Crypto key handler has to be used by the stack. It is the application’s responsibility to create the key. The old emberSetSecurityKey()no longer designates the key used by the network. It can be used to erase an old key from its previous location in NVM.•Added a new API emberRemovePsaSecurityKey()that cancels the effects of emberSetPsaSecurityKey(). It does not erase the key. It is the application’s responsibility to destroy the key.2.2 ImprovementsNone2.3 Fixed IssuesFixed in release 3.4.0.0833232 Fixed an error the was causing Connect Application Framework IPC to write to the address 0.2.4 Known Issues in the Current ReleaseIssues in bold were added since the previous release. If you have missed a release, recent release notes are available on the TECH DOCS tab on https:///developers/gecko-software-development-kit.When running the RAIL Multiprotocol Library (used forexample when running DMP Connect+BLE), IR Calibrationis not performed because of a known issue in the RAILMultiprotocol Library. As result, there is an RX sensitivityloss in the order of 3 or 4 dBm.501561 In the Legacy HAL component,the PA configuration is hard-coded regardless of the user or board settings. Until this is changed to properly pull from the configuration header, the file ember-phy.c in the user's project will need to be modified by hand to reflect the desired PA mode, voltage, and ramp time.711804 Connecting multiple devices simultaneously may fail with a timeout error.2.5 Deprecated ItemsNone2.6 Removed ItemsNoneRAIL Applications 3 RAIL Applications3.1 New ItemsAdded in release 3.4.0.0•EFR32xG24 support•FGM230S support•RAIL Bluetooth DMP - SoC Range Test BLE and IEEE802.15.4 demos for some XGM210 boards3.2 ImprovementsNone3.3 Fixed IssuesNone3.4 Known Issues in the Current ReleaseNone3.5 Deprecated ItemsNone3.6 Removed ItemsNone4 RAIL Library4.1 New ItemsAdded in release 3.4.0.0•The RAIL channel of a received packet is now available in the packet's RAIL_RxPacketDetails_t::channel field. This can be of value when scanning or hopping across multiple channels while letting packets accumulate in the receive FIFO for later processing.•Added the RAIL_ConfigPaAutoEntry API to allow for easier configuration of PA auto mode operation in RAIL.•Added the RAIL_SetRssiDetectThreshold API to allow the user to detect when the RSSI is at or above a configurable threshold.Once configured, the RAIL_EVENT_DETECT_RSSI_THRESHOLD event can be used to detect when this happens.•Added support for the MGM240L022RNF module.•Added support for the FGM230SA27HGN and FGM230SBHGN modules.•Added the RAIL_GetChannelAlt API. This function returns the channel the radio is currently using. If using DMP and run on the inactive protocol it returns the channel that will be used when next switching to that protocol. When using channel hopping, mode switch, and other features that change channels dynamically this may be different than what is returned by RAIL_GetChannel, as this function will track what channel the radio is actually on at that moment and not what it started on.4.2 ImprovementsChanged in release 3.4.0.0•The "RAIL Utility, PTI" component will now validate that the correct set of pins are in use for the desired PTI mode.•RAIL will now error if attempting to start a CSMA or LBT transmit while a scheduled RX is still in progress or vice versa.•Added PA curves for BGM240P and MGM240P modules.•Restricted the SL_RAIL_UTIL_PA_RAMP_TIME_US to 10us on some EFR32 modules to match the certification conditions.4.3 Fixed IssuesFixed in release 3.4.0.0376658 Fixed an issue with the Bluetooth LE coded PHY on EFR32xG21 where a packet received with a corrupt coding indicator would result in an invalid start-of-packet timestamp.759793 Fixed an issue with Bluetooth LE long-range reception on EFR32xG21 that corrupted packet data and tripped RAIL_ASSERT_FAILED_UNEXPECTED_STATE_RX_FIFO.772769 Fixed an issue when running IR Calibration on the EFR32xG23 using RAIL_CalibrateIrAlt where we could compute an invalid IRCAL value for certain PHYs and chips.777427 Fixed support for using the signal identifier CCA modes simultaneously with a user-enabled signal identifier trigger event.819644 Fixed an issue with frame-type decoding PHYs running at more than 500 kbps on EFR32xG22 and later.825083 Fixed an issue on EFR32xG23 and EFR32xG24 where PTI could merge multiple receive packets into the same transaction when interrupt latency is significant.829499 Fixed an issue where RAIL_GetRadioStateDetail would not report the correct state information when frame detection was disabled or during an LBT operation.830214 Ensure that the RAIL_RadioConfigChangedCallback_t is called for all RAIL handles in a dynamic multiprotocol application where multiple handles use the same underlying PHY configuration.835299 Fixed an issue with dynamic handling of whitening and FCS in FSK when onlyRAIL_IEEE802154_E_OPTION_GB868 was enabled.844600 Fixed an issue of not being able to receive packets during a RAIL_ScheduleRx configured with a zero relative start time when Power Manager sleep is enabled and configured with an EM2 or lower energy requirement.4.4 Known Issues in the Current ReleaseIssues in bold were added since the previous release.Using direct mode (or IQ) functionality on EFR32xG23requires a specifically set radio configuration that is notyet supported by the radio configurator. For theserequirements, reach out to technical support who couldprovide that configuration based on your specification 641705 Infinite receive operations where the frame's fixed lengthis set to 0 are not working correctly on the EFR32xG23series chips.732659 On EFR32xG23:•Wi-SUN FSK mode 1a exhibits a PER floor with fre-quency offsets around ± 8 to 10 KHz• Wi-SUN FSK mode 1b exhibits a PER floor with fre-quency offsets around ± 18 to 20 KHz819544 Rx duty cycle mode does not work reliably on theEFR32xG24 platform.818707 BLE CTE timings are sometimes slightly off when usingthe EFR32xG24 with a 38.4MHz crystal.4.5 Deprecated ItemsNone4.6 Removed ItemsNone5 Using This ReleaseThis release contains the following•Radio Abstraction Interface Layer (RAIL) stack library•Connect Stack Library•RAIL and Connect Sample Applications•RAIL and Connect Components and Application FrameworkThis SDK depends on Gecko Platform. The Gecko Platform code provides functionality that supports protocol plugins and APIs in the form of drivers and other lower layer features that interact directly with Silicon Labs chips and modules. Gecko Platform components include EMLIB, EMDRV, RAIL Library, NVM3, and mbedTLS. Gecko Platform release notes are available through Simplicity Studio’s Documentation tab.For more information about the Flex SDK v3.x see UG103.13: RAIL Fundamentals and UG103.12: Silicon Labs Connect Fundamentals. If you are a first time user, see QSG168: Proprietary Flex SDK v3.x Quick Start Guide.5.1 Installation and UseThe Proprietary Flex SDK is provided as part of the Gecko SDK (GSDK), the suite of Silicon Labs SDKs. To quickly get started with the GSDK, install Simplicity Studio 5, which will set up your development environment and walk you through GSDK installation. Simplicity Studio 5 includes everything needed for IoT product development with Silicon Labs devices, including a resource and project launcher, software configuration tools, full IDE with GNU toolchain, and analysis tools. Installation instructions are provided in the online Simplicity Studio 5 User’s Guide.Alternatively, Gecko SDK may be installed manually by downloading or cloning the latest from GitHub. See https:///Sili-conLabs/gecko_sdk for more information.Simplicity Studio installs the GSDK by default in:•(Windows): C:\Users\<NAME>\SimplicityStudio\SDKs\gecko_sdk•(MacOS): /Users/<NAME>/SimplicityStudio/SDKs/gecko_sdkDocumentation specific to the SDK version is installed with the SDK. Additional information can often be found in the knowledge base articles (KBAs). API references and other information about this and earlier releases is available on https:///.5.2 Security InformationSecure Vault IntegrationWhen deployed to Secure Vault High devices, sensitive keys are protected using the Secure Vault Key Management functionality. The following table shows the protected keys and their storage protection characteristics.Thread Master Key Exportable Must be exportable to form the TLVsPSKc Exportable Must be exportable to form the TLVsKey Encryption Key Exportable Must be exportable to form the TLVsMLE Key Non-ExportableTemporary MLE Key Non-ExportableMAC Previous Key Non-ExportableMAC Current Key Non-ExportableMAC Next Key Non-ExportableWrapped keys that are marked as “Non-Exportable” can be used but cannot be viewed or shared at runtime.Wrapped keys that are marked as “Exportable” can be used or shared at runtime but remain encrypted while stored in flash.For more information on Secure Vault Key Management functionality, see AN1271: Secure Key Storage.Security AdvisoriesTo subscribe to Security Advisories, log in to the Silicon Labs customer portal, then select Account Home. Click HOME to go to the portal home page and then click the Manage Notifications tile. Make sure that ‘Software/Security Advisory Notices & Product Change Notices (PCNs)’ is checked, and that you are subscribed at minimum for your platform and protocol. Click Save to save any changes.5.3 SupportDevelopment Kit customers are eligible for training and technical support. Use the Silicon Labs Flex web page to obtain information about all Silicon Labs Thread products and services, and to sign up for product support.You can contact Silicon Laboratories support at /support.Silicon Laboratories Inc.400 West Cesar Chavez Austin, TX 78701USAIoT Portfolio/IoTSW/HW/simplicityQuality /qualitySupport & Community/communityDisclaimerSilicon Labs intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software imple-menters using or intending to use the Silicon Labs products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and “Typical” parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Labs reserves the right to make changes without further notice to the product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the included information. Without prior notification, Silicon Labs may update product firmware during the manufacturing process for security or reliability reasons. Such changes will not alter the specifications or the performance of the product. Silicon Labs shall have no liability for the consequences of use of the infor -mation supplied in this document. This document does not imply or expressly grant any license to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any FDA Class III devices, applications for which FDA premarket approval is required or Life Support Systems without the specific written consent of Silicon Labs. A “Life Support System” is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant personal injury or death. Silicon Labs products are not designed or authorized for military applications. Silicon Labs products shall under no circumstances be used in weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering such weapons. Silicon Labs disclaims all express and implied warranties and shall not be responsible or liable for any injuries or damages related to use of a Silicon Labs product in such unauthorized applications. Note: This content may contain offensive terminology that is now obsolete. Silicon Labs is replacing these terms with inclusive language wherever possible. For more information, visit /about-us/inclusive-lexicon-projectTrademark InformationSilicon Laboratories Inc.®, Silicon Laboratories ®, Silicon Labs ®, SiLabs ® and the Silicon Labs logo ®, Bluegiga ®, Bluegiga Logo ®, EFM ®, EFM32®, EFR, Ember ®, Energy Micro, Energy Micro logo and combinations thereof, “the world’s most energy friendly microcontrollers”, Redpine Signals ®, WiSeConnect , n-Link, ThreadArch ®, EZLink ®, EZRadio ®, EZRadioPRO ®, Gecko ®, Gecko OS, Gecko OS Studio, Precision32®, Simplicity Studio ®, Telegesis, the Telegesis Logo ®, USBXpress ® , Zentri, the Zentri logo and Zentri DMS, Z-Wave ®, and others are trademarks or registered trademarks of Silicon Labs. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. Wi-Fi is a registered trademark of the Wi-Fi Alliance. All other products or brand names mentioned herein are trademarks of their respective holders.。

masm9.0宏汇编ml.exe完整命令行参数解释masm9.0是微软VC2008里附带的最新版的宏汇编器,现列出全部命令行参数解释,希望对大家学习WIN32汇编有用./AT Enable tiny model (.COM file)/AT 允许微型内存模式。

对与.COM文件格式的要求互相冲突的代码给出错误信息。

注意该选项和.MODEL TINY伪指令并不完全相同/Bl<linker> Use alternate linker/Bl filename 选择其他的连接器/c Assemble without linking/c 只编译，不连接/coff generate COFF format object file/coff 生成Microsoft公共目标文件格式(common object file format)的目标文件/Cp Preserve case of user identifiers/Cp 保留所有用户定义标识符的大小写/Cu Map all identifiers to upper case/Cu 映射所有标识符的大小写/Cx Preserve case in publics, externs/Cx 保留公共和外部符号的大小写(默认)/D<name>[=text] Define text macro/D sysmbol[=value] 定义给定名字的文本宏。

如果没有value部分，文本宏为空。

定义中以空格隔开的多个符号必须以引号引起来。

/EP Output preprocessed listing to stdout/EP 输出预处理列表到标准输出/errorReport 发送编译器内部错误给微软(这个新增)/F <hex> Set stack size (bytes)/F hexnum 设置堆栈大水(字节),(这与/link /STACK:number是相同的)。

mkimage参数1. -A, --arch <arch>：指定目标平台的体系结构（如arm、x86、powerpc等）。

2. -O, --os <os>：指定目标平台的操作系统类型（如linux、vxworks、netbsd等）。

3. -T, --type <type>：指定生成的镜像文件的类型（如kernel、ramdisk、multi等）。

指定压缩算法，可以是none、gzip，或者bzip25. -d, --datafile <filename>：指定输入文件的名称，用于生成镜像文件。

6. -n, --name <name>：指定生成的镜像文件的名称。

7. -t, --text-base <address>：指定生成镜像文件时，text段的基地址。

8. -s, --loadaddr <address>：指定生成镜像文件时，加载地址（即文件在内存中的起始地址）。

9. -e, --entry <address>：指定生成镜像文件时，程序入口地址。

10. -a, --args <arg-string>：指定生成镜像文件时，程序的启动参数。

11. -p, --vendor-place <addr>，--place <pl>：声明文件中的字段分配的地址，可以指定多个地址。

12. -c, --custom-header <custom-header>：指定生成镜像文件时，自定义的头部信息。

13. -H, --header-version <header-version>：指定生成镜像文件时，头部信息的版本。

14. -r, --reuse-dtb <dtb-file>：指定一个设备树二进制文件，以便在生成镜像时重用设备树段。

15. -D, --disable <dtb-sections>：禁用指定的设备树文件段。

Flex布局参数分析flex布局很好⽤，优点很多：静态流⽂件，空间概念，主流样式可以简单调整，同时⽀持bfc，空间可以动态分配，专业⼀维空间布局这么多优点，所以要提倡使⽤弹性布局。

空间设置：flex的⽅向、定位这些可以再⽗节点设置。

内部单项设置：可扩展，可压缩，占⽐，剩余空间占⽐，独⽴对齐。

这些需要在⼦节点设置。

就需要学会配置，可以简写的flex-item的属性：flex-grow | flex-shrink | flex-basis，另外还有order | align-self。

数字和auto，举个例⼦：flex: 1 auto; // flex: auto 效果⼀样浏览器解析后是这样：两个可变属性，被定为1，最后的基本宽⾼设置为auto，说明flex的优先级最⾼的属性是 flex-basis，以此值为点做调整。

flex-grow: 1;flex-shrink: 1;flex-basis: auto;none，⼀类特殊设置：flex: none; // 失去弹性效果，和 display：block; width: auto; 效果⼀样，注意：设置有 none 再加其他值不合法。

浏览器解析后：flex-grow: 0;flex-shrink: 0;flex-basis: auto;⼀个数字的情况：flex: 1;浏览器解析后：平时喜欢⾮⼦节点都是这上flex: 1，就是这样的情况，所有item⼦节点同时参数收缩和增长空间的处理，所以可以按⽐例划分。

flex-grow: 1;flex-shrink: 1;flex-basis: 0%;两个数字的情况：flex: 2 1;浏览器解析后：flex-grow: 2;flex-shrink: 1;flex-basis: 0%;三个数字的情况flex: 2 1 2; // 不合法，基础值必须是可⽤的单位，如百分⽐，px，em这些具体单位。

flex: 2 2 5%; // 嗯，这样合法。

Flexsim常用函数的使用方法基本建模函数和逻辑表达式这里给出Flexsim中常用命令的快捷参考。

参见命令集可获取更多有关这些命令的详细信息。

实体参量下列的命令和存取变量在Flexsim中被用作实体引用。

变量current和item∙current -变量current是当前资源实体的引用。

通常可以是下拉菜单中的一个存取变量。

∙Item -变量item是某触发器或函数所涉及的临时实体引用。

通常可以是下拉菜单中的一个存取变量。

引用命令实体属性实体空间属性实体标签表实体控制高级函数实体变量参见任务序列，可以获得更多有关控制任务执行器的信息。

提示和界面输出更多高级函数下面是可能使用到的更多高级函数。

这里没有提供参数列表，参见命令集可获得更多信息。

节点命令- node(), nodeadddata(), getdatatype(), nodetopath(), nodeinsertinto(), nodeinsertafter(), getnodename(), setnodename(), getnodenum(), getnodestr(), setnodenum(), setnodestr(), inc()；数据交换命令- stringtonum(), numtostring(), tonum(), tonode(), apchar()；节点表命令- setsize(), cellrc(), nrows(), ncols()；模型运行命令- cmdcompile(), resetmodel(), go(), stop()；3D个性化绘制代码命令- drawtomodelscale(), drawtoobjectscale(), drawsphere(), drawcube(), drawcylinder(), drawcolumn(), drawdisk(), drawobject(), drawtext(), drawrectangle(), drawline(), spacerotate(), spacetranslate(), spacescale()；Excel命令- excellaunch(), excelopen(), excelsetsheet(), excelreadnum(), excelreadstr(), excelwritenum(), excelwritestr(), excelimportnode(), excelimporttable(), excelclose(), excelquit()；ODBC命令- dbopen(), dbclose(), dbsqlquery(), dbchangetable(), dbgetmetrics(), dbgetfieldname(), dbgetnumrows(), dbgetnumcols(), dbgettablecell(), dbsettablecell()；运动学命令- initkinematics(), addkinematic(), getkinematics(), updatekinematics(), printkinematics()。

Flex SDK 编码规范及最佳实践（资料共享）注意:本文档目前还不完整且有些部分以TBD(待讨论)标记, 但这对于起步已经足够了!引言这篇文档拟定了用AS3编写开源Flex框架组件的编码规范. 遵照这些规范可以使得源代码看起来组织良好,风格一致并且更加专业.其中有些规范是很任意的,因为并非总存在一种”最好方式”来编码. 然而,为了照顾一致性的要求,所有付诸Flex SDK的项目都将遵循这些编码规范.目录命名∙缩写词∙缩略语∙单词定界∙类型指定名∙包名∙文件名∙命名空间名∙接口名∙类名∙事件名∙样式名∙字符串属性枚举值∙常量名∙属性(变量和ge tter/setter) 名∙存储变量名∙方法名∙事件处理方法名∙参数名∙资源包名∙资源键名∙杂项名语言用法∙编译选项∙基于属性的APIs∙类型定义∙Literals∙Expressions∙Statements∙Declarations文件组织∙Copyright notice∙package statement∙import statements∙use namespace statement∙Class metadata∙Class declaration∙include statement for Version.as ∙Implementation notes∙Class initialization∙Class constants∙Class mix-ins∙Class resources∙Class variables∙Class properties∙Class methods∙Constructor∙Variables∙Overridden properties∙Properties∙Overridden methods∙Methods∙Overridden event handlers∙Event handlers∙Out-of-package helper classes 格式化∙Line width∙Indentation∙Section separators∙Separation of declarations∙Metadata∙Array indexing∙Commas∙Array literals∙Object literals∙Function literals∙Type declarations∙Operators and assignments∙Statements∙Constant and variable declarations∙Function declarations∙Function calls∙if statements∙for statements∙switch statements∙class and interface declarationsASDoc文档∙Property comments命名编码时采用合适的命名既便于使用且理解起来也更为容易.所以你得在选择好的命名方式二多费心力,特别是针对公共API提供出来的时候.我们的命名规范绝大部分和ECMAScript和Flash Player 9 是一致的.缩写词作为通用规则而避免使用.例如calculateOptimalValue()比calcOptVal()的命名方式更优.表意明确比为了少敲几下代码而采用缩写更为重要. 如果你不使用缩写,开发人员就不用非得记住你是否采用了单词简写,如把”qualified”简写成”qual”或”qlfd”.不过,我们已经标准化了一些缩写词:∙acc 代表accessibility, 比如ButtonAccImpl∙auto 代表automatic, 比如autoLayout∙eval 代表evaluate, 比如EvalBindingResponder∙impl 代表implementation, 比如ButtonAccImpl∙info 代表information, 比如GridRowInfo∙num 代表number of, 比如numChildren∙min 代表minimum, 比如minWidth∙max 代表maximum, 比如maxHeight∙nav 代表navigation, 比如NavBar∙regexp 代表regular expression, 比如RegExpValidator∙util 代表utility, 比如StringUtil上述列表可能没有包含目前使用的所有缩写词.如果你用到了上面没有列举出来的缩写词,请搜索源代码看是否已经有相应的缩写词使用了.如果没发现,再考虑一下如果缩写是否合适.有时我们(故意)采用的缩写词不一致.例如,我们在很多时候都会拼写”horizontal”和”vertical”，像horizontalScrollPolicy和verticalScrollPolicy。