SDK使用说明
T5 longan linux SDK 开发环境配置手册说明书
T5longan linux SDK 开发环境配置手册V1.3Revision HistoryVersion Date Author Changes compared to previous issue V0.12019-12-17吴松睿初建版本V0.22020-4-2袁国超添加编译、QT、工具链、测试等章节V0.32020-5-9xufang补充rootfs工具说明V1.02020-5-10袁国超添加auto sdk等章节V1.12020-7-4袁国超添加显示配置V1.22021-12-3KPA0501增加T507-H/T517-H的编译说明V1.32022-04-28KPA0501更新-H系列编译说明目录1.概述 (6)2.目录结构 (7)2.1.buildroot (7)2.2.kernel (8)2.3.brandy (8)2.4.platform (8)2.5.tools (9)2.6.test系统dragonboard (9)2.7.device (10)3.开发环境配置 (12)3.1.Linux服务器开发环境搭建 (12)3.1.1.硬件配置 (12)3.1.2.系统版本 (12)3.1.3.网络环境 (13)3.1.4.软件包 (13)3.2.Windows PC环境搭建 (13)3.2.1.开发工具安装 (13)3.2.2.开发板驱动安装 (14)3.2.3.烧录软件安装 (14)3.3.开发板介绍 (15)3.3.1.使用准备 (16)3.3.2.开发板供电 (16)3.3.3.串口连接 (16)B调试连接 (17)3.3.5.摄像头硬件连接 (17)4.编译代码和打包固件 (18)4.1.编译基础 (18)4.1.1.基本编译命令 (18)4.1.2.编译选项 (18)4.1.3.扩展编译命令 (19)4.2.编译示例 (20)4.2.1.配置环境 (20)4.2.2.T5auto编译详解 (21)4.2.3.T5Qt编译详解 (22)4.3.工具链简介 (22)4.3.1.Kernel工具链 (23)4.3.2.Buildroot工具链 (23)4.3.3.Dragonboard工具链 (23)5.固件烧写 (24)B烧录 (24)5.1.1.运行PhoenixSuit (24)5.1.2.连接设备 (24)5.1.3.选择img文件 (25)5.1.4.开始烧录 (25)5.2.SD卡烧录 (27)5.2.1.制作升级卡 (27)5.2.2.插入平台上电升级 (27)6.系统调试 (28)6.1.串口登录命令行 (28)6.2.连接成功后，在串口终端回车即可。
ABB PC SDK 5.15 用户手册说明书
Release NotesPC SDK5.15Revision: -Table of Contents The information in this manual is subject to change without notice and should not be construed as acommitment by ABB. ABB assumes no responsibility for any errors that may appear in this manual.Except as may be expressly stated anywhere in this manual, nothing herein shall be construed as any kind of guarantee or warranty by ABB for losses, damages to persons or property, fitness for a specific purpose or the like.In no event shall ABB be liable for incidental or consequential damages arising from use of this manual and products described herein.This manual and parts thereof must not be reproduced or copied without ABB's written permission, and contents thereof must not be imparted to a third party nor be used for any unauthorized purpose. Contravention will be prosecuted.Additional copies of this document may be obtained from ABB at its then current charge.© Copyright 2012 ABB All rights reserved.ABB ABRobotics ProductsSE-721 68 VästeråsSweden© Copyright 2012 ABB All rights reserved 2ContentsOverview 5 1 Release Information 61.1 General 61.2 Contents 62 What’s New in this Release? 72.1 Robot Communication on Developer Center 73 Late-breaking information 83.1 Overview 84 Problems Corrected 94.1 Solved Product Defect Documents (PDD) since PC SDK5.14.03 95 Known Limitations 106 Installation Information 126.1 Hardware and Software requirements 136.2 Compatibility 147 Technical Support 15OverviewDescriptionThis document provides information about the new features, problems corrected, andinstallation of PC SDK.Product OverviewPC SDK can be used to develop customized PC applications, for communication withthe IRC5 controller.It can also be used to develop RobotStudio add-ins that interacts with the IRC5controller.PC SDK applications can connects to one or several IRC5 controllers, real as well asvirtual.No license is required to develop applications using PC SDK.The option “PC Interface” is required to allow PC SDK applications to connect to theIRC5 controller over LAN network.For download, updates and information, visit the RobotStudio Community:/roboticssoftware.To get started, or to learn more, visit our Developer Center:Here you will also find the User Forum, where developers discuss software problemsand solutions online:/forum1 Release Information1.1 GeneralRelease NameThe release name is PC SDK 5.15 and the build number is 5.15. 0261.Release DateThe release date is 12th of October, 2012.1.2 Contents.NET AssembliesABB.Robotics.dllABB.Robotics.Controllers.dllRedistributablesABBControllerAPI.msmRobot Communication Runtime installerDocumentationReference Manual – PC SDK (Html Help). Documentation of class libraries with methodsignatures in C# and Visual Basic.Application Manual – PC SDK (Html Help and PDF).After installation the documentation can be launched from the Windows Start MenuPrograms\ABB Industrial IT\Robotics IT\Robot Studio 5.15\SDK.The manuals and additional samples are also available at.2 What’s New in this Release?OverviewThis section contains information about new features in this release.2.1 Robot Communication on Developer CenterYou can now access the PC SDK Application and Reference Manual from.To help you get started you will also find complete walk-through projects for download.3 Late-breaking information3.1 OverviewThis section contains late-breaking information that will be included in the appropriatedocuments in the subsequent releases.Nothing in this release.4 Problems CorrectedOverviewThis section describes the problems solved in PC SDK.4.1 Solved Product Defect Documents (PDD) since PC SDK5.14.03ID Title- Controller.IOSystem.GetSignals performancedegraded in 5.14.03PDD308 Old PC SDK Apps not working with/against RW5.14.025 Known LimitationsOverviewThis section describes known limitations in PC SDK.*Value of RAPID data exeeding 1024 bytes cannot be retrievedIt is not possible to retrieve a value of a RAPID data exceeding 1024 bytes.An instance of a large RECORD may exeed this limition, as well as an array of suchrecords, for example.Workaround 1: Make your data smaller in size, for example by using two smaller records with less elements in each, instead of one large record with lots of elements.Workaround 2: Do not retrieve the entire value of a RAPID array. Instead retrieve thevalue element by element. Prefer using RapidData.ReadItem(i), over ArrayData[i].PC SDK UIInstructionEvent / RAPID UIListViewUIListViewEventArgs.ListItems may return the wrong number of list items if - if youare using characters like double quote (“) and brackets ([ ]) in the RAPID array of listitem strings, theAvoid using double quote (“) and brackets ([ ]).FlexPendant may lock up when PC SDK application release and immedeatley request mastershipIn manual mode, when a PC SDK application releases master and immediatelyrequests master again, the FlexPendant is locked up when the user presses theprompt to grant write access to the PC SDK application. In automatic mode there isno problem.IPC Messaging - PC SDK always sends 444 bytes of dataWhen sending a message with IpcQueue.Send(), the size of the message sentover the network will be 444 bytes, regardless of the amount of data passed toSend(). Data must therefore be null terminated.IPC Messaging requires MTA threadIpcQueue.Send() must be called from an MTA thread. Create a separate senderthread and use the method Thread.SetApartmentState() to set the apartmentstate to MTA before starting it.IsLocal on the class RapidData, returns true for shared dataThe property IsLocal on the class RapidData, returns true for shared data, eventhough such data is visible from all modules.The declarations of default zonedata and speeddata has been moved from moduleBASE.SYS in each task, and are now installed as shared data.If an application used to create a RapidData object representing for example"v1000", the IsLocal property returned false in RobotWare 5.12, but will return truein RobotWare 5.13."6 Installation InformationOverviewTo install PC SDK click RobotStudio on the RobotWare & RobotStudio DVD.If you select the default installation option Complete, PC SDK will be installed. If youwant to install only PC SDK and not RobotStudio select the installation option Custom.PC SDK 5.xx will be installed side by side with any previous major version of PC SDK5.xx, while minor versions within a release will update to the latest one.Microsoft Visual Studio development environment is used to develop PC SDKapplications.Refer to chapter 6.1 for a list of supported versions of Visual Studio.The default installation path is C:\Program Files\ABB Industrial IT\Robotics IT\SDK\PCSDK 5.15.6.1 Hardware and Software requirementsSoftware requirementsPC software requirementsOperating SystemsMicrosoft Windows XP SP3 – 32bit editionMicrosoft Windows 7 – 32bit editionMicrosoft Windows 7 – 64bit editionMicrosoft Windows 8 – 64 bit editionRobot Communication RuntimePC SDK applications requires Robot Communications Runtime to be installed on thePC. The runtime is installed by RobotStudio installation, and can also be installedseparately from C:\Program Files\ABB Industrial IT\Robotics IT\SDK\PC SDK5.15.xx\redistributable\RobotCommunicationRuntime after you have installed PC SDK.Redistributables for earlier versions of PC SDK can be found onRobotStudioRobotStudio 5.15 is needed for building virtual controller systems and fordebugging and testing in the virtual environment.Please see /forum for more information.IRC5 software requirements- RobotWare option "PC Interface" for communication with IRC5 controller.Supported development environmentsMicrosoft Visual Studio 2008Express edition or better.Microsoft Visual Studio 2010Express edition or better.Microsoft Visual Studio 2012Express edition or better.6.2 CompatibilityThe APIs in PC SDK 5.15.xx are backwards compatible with the APIs in PC SDK5.14.There are no breaking changes.PC SDK communicates with the robot controller using the Robot CommunicationRuntime, which is designed to be backwards compatible with earlier versions ofRobotWare.Note! Functionality introduced in later versions of RobotWare will not be available for aPC SDK application that is connected to a controller with an older version ofRobotWare.For example the Messaging functionality is only supported on RobotWare 5.10 andabove. This means that a PC SDK application cannot use the Ipc class whencommunicating with a controller with RobotWare 5.09.The code will compile, but an exception will be thrown at runtime. Applicationdevelopers are responsible for handling this scenario in their applications. Please referto the PC SDK Reference Documentation for details.Note! Compatibility between RobotWare minor revisions is guaranteed (PC SDK5.15.01 will be compatible with PC SDK/RW 5.15.02 etc)..7 Technical SupportFor technical support please turn to your local ABB office./contactsFor help, advice and the latest updates please visit the User Forum./forum。
qq互联.Android_SDK_V2.0使用说明
Android_SDK_V2.0使用说明1.Android_SDK_V2.0简介Android SDK以Jar包形式提供，封装了QQ登录的登录授权以及大部分OpenAPI 和社交渠道的分享、邀请、请求礼物、挑战炫耀、语音、评价等API，移动应用只需要修改少量代码，即可快速实现QQ登录功能，并可调用平台提供的OpenAPI及社交渠道API 的功能。
Android平台上的应用，要使用QQ互联平台提供的Android SDK，请先在QQ互联平台进行注册，获取appid和appkey。
SDK主要提供的功能接口有：登录、注销、邀请好友、应用分享、获取用户信息、获取用户相册列表、发送分享、发表说说、发表微博、上传图片、创建相册、设置QQ头像、增量授权、分享消息给QQ好友（图文消息，纯图片和音乐）、发送语音等功能，Android_SDK_V2.0新增了发表语音，分享到QQ空间等新功能。
详细内容可参考《接口调用说明》。
更多详细信息请查看API列表。
2.下载Android SDK请到SDK下载页面下载Android SDK和示例代码。
3.创建工程及引用SDK源码文件以下以eclipse为开发的IDE进行范例说明：Eclipse ADT ADT 17 以上版本用户，请在工程目录下新建一个文件夹libs，将open-sdk.jar文件和mta_sdk_x.x.x.jar文件拷贝到这个文件夹下，然后在Eclipse里面刷新工程即可完成SDK文件的引入。
1.7以下版本的用户请参考下面的步骤引入SDK文件：（1）创建一个工程，并把open-sdk.jar文件和mta_sdk_x.x.x.jar文件拷贝到libs（或lib）目录下，如下图所示：（2）将open-sdk.jar加入编译路径中。
具体的操作步骤为：选中open-sdk.jar，右键菜单中选择Build Path，选择Add to Build Path，如下图所示：（3）将mta_sdk_x.x.x.jar加入编译路径中。
SDK接口说明(HTTP
查询余额
输入参数
参数
说明
类型
Account
帐号
String
Password
密码
String
Channel
通道
String
输出参数等于0的数字
剩余条数
–1
账号或密码错误
–2
还没开通短信通道，充值即可开通
调用方式：
/GetBalance.asp?Account=***&Password=***&Channel=***
备注：
编码：GBK提交方式：POST多个号码请用“逗号”分隔
–1
账号或密码错误
–2
还没开通短信通道，充值即可开通
–3
短信内容含有敏感字符
–4
短信内容字数超过了限值
–5
手机号码有错误
–6
该通道余额不足，不能满足本次发送
调用方式：
/SendSms.asp?Account=***&Password=***&Phones=***&Content=***&Channel=***
群发短信
输入参数：
参数
说明
类型
Account
账号
String
Password
密码
String
Phones
发送手机号码（以英文,分隔）
String
Content
发送内容（需要UrlEncode）
String
Channel
通道
String
输出参数：
输出返回值参数
状态说明
0,xx,yy
发送成功（0表示成功，xx号码数，yy短信数）
SDK2.2技术说明文档
防区旁路恢复：没有旁路恢复信息（操作24小时防区时直接上旁路信息，再操作防区旁路编码，旁路恢复）
子系统跳转：1234##（第一子系统）1234####（第二子系统）依次累加
进入编程：9876#0
退出编程：L*
枫叶728主机：
布防：474747或4747
3.状态码查询支持主机类型新增了vista120，MTA311，CC408，vista20p，DS7400，DS7240
4.键盘序列帧不支持修改主机编程项内容
5.SDK_DEMO中配置文件config是为vista120主机专用（120主机使用j8口传输数据）
6.CK主机使用键盘序列帧多防区旁路时，只能连续旁路5个防区
5．点击布防按钮，提示信息如下，则表明SDK回控成功
附录三
SDK_DEMO支持接入的各主机使用虚拟键盘的基本操作说明
CK系列：
布防1234#
撤防1234#
防区旁路1234C防区号（1）#
防区旁路恢复1234C防区号（1）#
进入编程012345*0#
退出编程*#
MTA311主机：
布防1234#
撤防1234#
修改帐号：指修改模块ID号
修改类型：指主机的类型
虚拟键盘地址：指主机的键盘地址
虚拟键盘：指模拟各类型主机的键盘
获取模块数量：指查询当前模块在线个数
继电器控制：指模拟联动模块，控制联动模块
状态查询：指查询CK系列及MTA311主机的当前状态
附录一
SDK回控设置步骤说明
1．打开M_51NET设置软件，选择开始搜索，选中需要下载的模块
7.SDK缓存数量为100000条
acrobat sdk 接口说明
acrobat sdk 接口说明Acrobat SDK是一个强大的工具包，它可以提供PDF文档的编辑和操作功能，例如将页面进行旋转、添加文本、创建表格等。
在这个工具包中，API是一个重要的部分，因为它使得开发者能够轻松地使用Acrobat SDK来实现自己所需要的功能。
因此，在这篇文章中，我们将围绕着Acrobat SDK的API来进行阐述，帮助您更好地理解和使用它。
步骤一：选择开发环境首先，要想使用Acrobat SDK，您需要选择一个适合自己的开发环境。
Acrobat SDK支持多种编程语言，例如C++，Java，C#等等。
同时它也支持很多的操作系统，例如Windows、macOS、Linux等等。
因此，您可以根据自己的开发需求来选择合适的编程语言和操作系统。
如果您是一个新手，建议选择比较容易上手的编程语言来开发，例如Python或Java。
步骤二：安装Acrobat SDK安装Acrobat SDK非常简单。
首先，您需要到Adobe官网下载Acrobat SDK并且进行安装。
在安装之前，您需要确定安装的版本和适用的操作系统。
如果您选择的是Windows操作系统，需要先确认您的Windows是32位还是64位版本。
另外，如果您的操作系统是macOS或Linux，需要确认您已经安装了对应的开发环境。
一旦安装完成之后，您就可以开始使用Acrobat SDK来进行开发工作了。
步骤三：使用Acrobat SDK APIAcrobat SDK提供了很多的API，这些API可以用来进行PDF文档的编辑和操作。
例如，您可以使用API来打开一个PDF文档、将文档保存为另一个格式、创建一个新的页面、添加文本、旋转页面等等。
这些API的用法非常简单，只需要按照Acrobat SDK的API文档说明进行调用即可。
当然，在使用这些API的时候，您需要进行一些必要的参数设置和错误处理，以确保您的开发工作不会出现问题。
Functional Mockup Unit（FMU）软件开发工具包（SDK）2.0.6说明书
FMU SDK 2.0.6The FMU SDK is a free software development kit provided by Synopsys. The FMU SDK demonstrates basic use of Functional Mockup Units (FMUs) as defined by the following specifications •Functional Mock-up Interface for Model Exchange and Co-Simulation 2.0 (July 25, 2014)•Functional Mock-up Interface for Model Exchange 1.0 (January 26, 2010)•Functional Mock-up Interface for Co-Simulation 1.0 (October 12, 2010)The FMI specifications are available from here. The FMU SDK can also serve as starting point for developing applications that create or process FMUs.For each of the supported FMI versions (currently 1.0 and 2.0), the FMU SDK contains the C sources for various discrete and continuous FMU models, a batch file for compiling and zip'ing these models, an XML parser for parsing the model description of an FMU and two simple simulation programs that run a given FMU and output the result as CSV file.For bug reports, questions or comments regarding the FMU SDK, please mail to ***********************. Questions or comments regarding the FMU specification should be sent to info@.Table of Contents•Building and Installing the FMU SDK•Simulating an FMU•Creating your own FMUs•FMU SDK Revision history•License conditionsInstalling the FMU SDKThe FMU SDK runs on all 32 bit and 64 bit Windows platforms, Linux and Mac OS X platforms. Unzip the file in a directory where you have write access. That directory is called FMUSDK_HOME below and may contain white space, such as in "C:\Program Files\fmusdk". The FMU SDK contains only the C sources of the FMUs and the simulators, not the executables, and should compile on all Windows, Linux and Mac OS X platforms.To build Windows 32 bit versions of all FMUs and simulators of the FMU SDK, double click on FMUSDK_HOME\install.bat. This should create fmus in FMUSDK_HOME\fmu10\fmu andFMUSDK_HOME\fmu20\fmu, as well as four simulators in FMUSDK_HOME\fmu10\bin and FMUSDK_HOME\fmu20\bin.To build Windows 64 bit versions of all FMUs and simulators, open a command shell and run "install -win64". This creates additional fmus in the x64 subdirectories in FMUSDK_HOME\fmu10\fmu and FMUSDK_HOME\fmu20\fmu, as well as additional simulators in FMUSDK_HOME\fmu10\bin\x64 andFMUSDK_HOME\fmu20\bin\x64. Building these 64 bit versions works also on 32 bit Windows platforms. Execution of the 64 bit simulators and fmus requires however a 64 bit version of Windows. Compilation using install.bat requires that you have installed one of Microsoft Visual Studio 2005 (VS8), 2008 (VS9), 2010 (VS10), 2012 (VS11), 2013 (VS12) or 2015 (VS14), for example the free Express Edition. To compile with another compiler, adapt the batch files.To build Linux or Mac OS X binaries of all FMUs and simulators, open command shell and run "make". The build requires that you have installed the C and C++ compilers, libexpat and libxml2 libraries. To install these dependencies on Linux you can use a package manager like "sudo apt install g++", "sudo apt install libexpat1-dev", "sudo apt install libxml2-dev".Simulating an FMUOn Windows, to run a given FMU with one of the FMU simulators, open a command shell in directory FMUSDK_HOME and run the command fmusimfmusim simulator model.fmu [tEnd [h [loggingOn [csvSeparator]]]] [-win64]simulator ..... cs10 or cs20 for co-simulation, me10 or me20 for model exchange, requiredmodel.fmu ..... path to FMU, relative to current dir or absolute, required tEnd .......... end time of simulation, optional, defaults to 1.0 sech ............. step size of simulation, optional, defaults to 0.1 secloggingOn ..... 1 to activate logging, optional, defaults to 0csvSeparator .. c for comma, s for semicolon, optional, defaults to c-win64 ........ to use a 64 bit simulator. By default, the 32 bit version is usedThis unzips the given FMU, parses the contained modelDescription.xml file, simulates the FMU from t=0 to t=tEnd, and writes the solution to file 'result.csv'. The file is written in CSV format (comma-separated values), using ';' to separate columns and using ',' instead of '.' as decimal dot to print floating-point numbers. To change the result file format, use the 'csv separator' option. The logging option activates logging of the simulated FMU. The FMI specification does not specify, what exactly to log in this case. However, when logging is switched on, the sample FMUs of the FMU SDK log every single FMU function call. Moreover, the fmusim simulators log every step and every event that is detected. Example command:> fmusim me10 fmu10/fmu/me/bouncingBall.fmu 5 0.1 0 sFMU Simulator: run 'fmu/bouncingBall.fmu' from t=0..5 with step size h=0.1, loggingOn=0, csv separator=';'Simulation from 0 to 5 terminated successfulsteps (51)fixed step size .. 0.1time events 0state events (14)step events 0CSV file 'result.csv' writtenOn Linux and Mac OS X get inspired by run_all target inside FMUSDK_HOME\makefile.To plot the result file, open it e.g. in a spread-sheet program, suchas Miscrosoft Excel or OpenOffice Calc. The figure below shows the result of the above simulation when plotted using OpenOffice Calc3.0. Note that the height h of the bouncing ball as computed byfmusim becomes negative at the contact points, while the true solution of the FMU does actually not contain negative height values. This is not a limitation of the FMU, but of fmusim_me, which does not attempt to locate the exact time of state events. To improve this, either reduce the step size or add your own procedure for state-event location to fmusim_me.Creating your own FMUsThe FMU SDK contains a few sample FMUs•dq the Dahlquist test function x = -k der(x)•inc increments an integer counter every second•values demonstrates the use of all scalar FMU data types•vanDerPol ODE with 2 continuous states•bouncingBall a bouncing ball that defines state eventsTo implement your own FMU using the FMU SDK, create a directory - say xy - in FMUSDK_HOME\fmu10\src\models, orFMUSDK_HOME\fmu20\src\models, and create files xy.c there. The name of the new directory and of the .c file must be the same. The content of the .c file should follow the existing FMU examples, see the comments in the example code. For FMI 1.0, add also file modelDescription.xml. The XML file must not containthe <implementation> element and the closing <fmiModelDescription> tag, because this is added automatically during build. For FMI 2.0, add file modelDescription_cs.xml and modelDescription_me.xml. When done with editing xy.c and the xml file (or files), open a command shell in FMUSDK_HOME\fmu10\src\models or inFMUSDK_HOME\fmu20\src\models to run the build command.On Windows, run command build_fmu me xy to build an FMU for model-exchange, or build_fmu cs xy to build an FMU for co-simulation. This should create a 32 bit FMU file xy.fmu in the corresponding subdirectory of FMUSDK_HOME\fmu10 or FMUSDK_HOME\fmu20. To build a 64-bit FMU, append option -win64 to the build command. For Linux and Mac OS X get inspired by all target insideFMUSDK_HOME\fmu10\src\models\makefile andFMUSDK_HOME\fmu20\src\models\makefile.The figure below might help to create or process the XML file modelDescription.xml. It shows all XML elements (without attributes) used in the schema files (XSD) for model exchange and co-simulation 1.0. Notation: UML classdiagram.For the case of FMU 2.0, see the corresponding overview figure in the FMI specification 2.0.FMU SDK Revision history•07.02.2010, Version 1.0o First releaseo demo FMI for Model Exchange 1.0•05.03.2010, Version 1.0.1o demo FMI for Model Exchange 1.0o bug-fix in fmuTemplate.c: fmiSetString now copies the passed string argument and fmiFreeModelInstance freesall string copieso fmusim/main.c: removed strerror(GetLastError()) from error messages•22.08.2011, Version 1.0.2o demo FMI for Model Exchange 1.0 and FMI for Co-Simulation 1.0o added support for FMI for Co-Simulation 1.0 (standalone, no tool coupling)o bug-fix in fmusim/main.c: added missing calls tofmiTerminate and fmiFreeModelInstance•07.03.2014, Version 2.0.0o demo FMI for versions 1.0 and 2.0 RC1o added support for FMI 2.0 RC1o added 64 bit supporto more compilers recognized by the installer•16.04.2014, Version 2.0.1o bug-fix in modelDescription.xml files: remove alias parameter, add derivative attribute to suitable variables o bug-fix in fmu20/fmuTemplate.c: allow modules to request termination of simulation, better time eventhandling, initialize() moved from fmiEnterInitialization tofmiExitInitialization, correct logging message format infmiDoStepo bug-fix in Co-Simulation and Model Exchange simulators: set fmu location for 1.0 and fmu resources location for2.0 at instantiation of model•02.07.2014, Version 2.0.2o added support for FMI 2.0 RC2o remove support for exporting FMI 2.0 RC1. Co-Simulation and Model Exchange simulators still support FMI 2.0 RC1 o fmi2setDebugLogging called with 0 categories, set all categories to loggingOn value•27.08.2014, Version 2.0.3o track all states of Model-exchange and Co-simulation and check the allowed calling sequences for FMI 2.0 o added explicit 'isTimeEvent' parameter for eventUpdate function in the user's modelso lazy computation of computed valueso bug-fix in modelDescription.xml: set initial attribute to local and output variables, add unknown variables in<ModelStructure><InitialUnknowns> section•20.10.2015, Version 2.0.4o added explicit 'isNewEventIteration' parameter for eventUpdate function in the user's modelso bouncingBall example improvement: demonstrate tunable parameters, avoid 'fall through effect' due to numericalcalculationo bug-fix: allow to declare real variables and zero states ina modelo bug-fix: allow to simulate FMI 2.0 RC1 modelso bug-fix: remove memory leaks and compilation warnings •8.12.2017, Version 2.0.5o added support for Linux and Mac OS X. Thanks toChristopher Brooks (https:///cxbrooks) o added support for building with Microsoft VS 2015o location of simulators changes toFMUSDK_HOME\fmu10\bin andFMUSDK_HOME\fmu20\bin instead of FMUSDK_HOME\bin o fmu20 build define DISABLE_PREFIX to not use prefixed FMI functionso fmu20 models declare source files inModelDescription.xmlo log error messages regardless of loggingOn flag when functions return fmi2Erroro bug-fix: allow to declare real variables and zero states •20.07.2018, Version 2.0.6o update libxml2.lib to work for windows 7 and Visual Studio 2013 and 2015o linux - give exec right to build_fmu.sh before executing ito copy .h model files with rsync to avoid missing file error License conditionsThe FMU SDK is provided by QTronic under the BSD License.FMU SDK licenseCopyright © 2008-2019, Synopsys, Inc. All rights reserved.The FmuSdk is licensed by the copyright holder under the BSD License(/licenses/bsd-license.html):Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:- Redistributions of source code must retain the above copyright notice,this list of conditions and the following disclaimer.- Redistributions in binary form must reproduce the above copyright notice,this list of conditions and the following disclaimer in the documentationand/or other materials provided with the distribution.THIS SOFTWARE IS PROVIDED BY SYNOPSYS INC. "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIESOF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.IN NO EVENT SHALL SYNOPSYS INC. BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.The following additional tools are distributed with the FMU SDK under their respective licenses•7z 4.57 by Igor Pavlov. Used here to zip and unzip FMUs, license is here.•eXpat 2.0.1 by James Clark. Used here to parse the modelDescription.xml file of an FMU 1.0, license is here.•libxml, the XML C parser and toolkit of Gnome. Used here to parse the modelDescription.xml file of an FMU 2.0, licenseis here.。
Weibo_Android_SDK使用手册
上图“ZIP”按钮，下载后解压缩可得到开发工具包。开发工具主要包含： Weibo.sdk.android.api(封装 Weibo.api 接口) Weibo.sdk.android.sso.demo（使用 sso 一个 Demo，包含调用 weibo.api 接口） Weibo.sdk.android.sso（基于 weibo.sdk.android 扩展的 sso 源码） Weibo.sdk.android（OAuth2.0 封装源码） Android 平台微博 SDK 说明文档（建议下载，方便开发） Weibo.sdk.android.sso.jar（必须下载，该 jar 封装了 weibo.api 和 sso 相关方法） 开发工具下载地址： 3. 搭建开发环境 环境需求：JDK+SDK+IDE（Eclipse）+ Weibo.sdk.android.sso.jar 此处基于 Weibo.sdk.android.sso.demo 为例。可以类比新建项目。 1) 在 Eclipse 中右键选择 Import，选择 Existing Projects into Workspace，从中 选 择 weibo.sdk.android.sso.demo 项 目 所 在 位 置 。 导 入 结 果 如 下 图 所 示 ：
配置授权回调页 授权回调页是为 OAuth2.0 认证机制中的登陆认证地址，用户登录完成后最后悔跳 转此地址。 须在应用中配置次跳转地址才能使用 SDK 完成用户登录。 授权回调页查看及 设置地址： 第三方应用主页应用信息高级信息OAuth2.0 授权设置。 如下图所示： 2)
注：在使用 SDK 时，配置授权毁掉也是必不可少的，若没有配置，则登陆完成后无 法检测到授权地址，就无法获取授权的 Token 等信息。此地址并非必须配置成能访问地 址，保证格式正确即可。 2. 下载 Android 终端开发工具包 在 新 浪 微 博 开 放 平 台 文 档 一 页 有 SDK 下 载 一 项 ， 找 到 IOS SDK 下 载 链 接 https:///mobileresearch/weibo_android_sdk/downloads ，打开后可打包 下载。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
一、安装M8SDK
1. 下载最新的软件开发工具包（SDK）;
2. 执行M8SDK.msi；
3. 按提示安装完成，完成安装后的文件夹结构如下：
Program Files
Windows CE Tools
wce600
M8SDK
Emulation ---- M8模拟器
Include ---- C/C++ 头文件 Lib ---- 库文件
Samples ---- 文档和例子
二、安装VS2005+SP1
三、如何创建M8应用程序
1. 打开VS2005，选择[文件]-[新建]-[项目]
项目类型选择：智能设备
模板选择：Win32 智能设备
输入项目的名称：M8Sample
点击确定后进入下一步
2. 选择下一步
3. 平台选择：选择M8SDK
4. 下一步后选择Windows 应用程序
5. 点击完成后VS2005自动生成一个程序框架，要想使用Meizu提供的界面库，我们不使用VS2005自动生成的程序框架。
删除M8Sample.cpp的所有内容
从SDK的安装目录中拷贝例子代码: Program Files\Windows CE
Tools\wce600\M8SDK\Samples\MZFC\mzfc_sample_01
拷贝mzfc_sample_01.cpp的所有内容，粘贴到M8Sample.cpp中
6. 配置项目设置
打开[项目] – [属性]
选择[链接器] – [输入] – [附加依赖项]
添加mzfc.lib –界面支持库
添加PlatformApi.lib –使用M8特殊硬件的支持库
添加CallInterface.lib –使用GPRS拨号的支持库
7. 如何使用 MZFC 的静态连接库？
随着固件版本的不断升级，MZFC 中某些函数接口可能会改变，如果使用动态链接mzfc.dll，会造成使用旧版SDK 编译生成的应用程序无法在新版的固件中正确运行，为
了解决这一问题，开发者可以选择静态链接MZFC 库：
步骤 6 中，不要使用mzfc.lib
按照步骤 6，添加mzfcs.lib(Release 版)或mzfcsd.lib(Debug 版)
[项目] – [属性] – [C/C++] – [预处理器] – [预处理定义]中添加：MZFC_STATIC
8. 编译生成应用程序。
9. 使用模拟器调试应用程序
在设备选择列表中选择：M8SDK Emulator
启动调试，模拟器会自动加载
可以和正常调试一样设置断点，查看程序运行状态等功能
10. 使用M8调试应用程序
在设备选择列表中选择：M8SDK ARMV4 Device
M8 设置中USB选择同步模式
连接M8至电脑中，安装ActiveSync驱动
连接至ActiveSync后，这时可以启动调试
应用程序会部署到M8中运行
11. 使用M8调试应用程序时，请把M8的固件升级到V0.8.0.3版本以上
四、发布应用程序
请使用CAB打包工具打包要发布的应用程序
要想应用程序出现在M8的桌面，需要在CAB文件中加入以下注册表信息：
[HKEY_LOCAL_MACHINE\SOFTWARE\Meizu\MiniOneShell\Main\你的应用名称]
"DisplayName"="Calculator" ；显示在桌面的名称
"ExecFileName"="\\windows\\Calculator.exe" ；应用程序可执
行文件路径
"ProgramID"="{52D0E792-4A35-4619-80B0-9204156D6F74}" ；GUID，请使用VS2005工具菜单下的生成GUID工具生成
"DefaultIcon"="\\windows\\calc8080.png" ；桌面图标
"Order"=dword:1 ；在当前桌面页中的位置
"Page"=dword:1 ；出现在桌面的第几页。