Directx Software Development Kit June 2010
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Building Openjfx
Building OpenJFX Building a UI toolkit for many different platforms is a complex and challenging endeavor. It requires platform specific tools such as C compilers as well as portable tools like Gradle and the JDK. Which tools must be installed differs from platform to platform. While the OpenJFX build system was designed to remove as many build hurdles as possible, it is necessary to build native code and have the requisite compilers and toolchains installed. On Mac and Linux this is fairly easy, but setting up Windows is more difficult. If you are looking for instructions to build FX for JDK 8uNNN, they have been archived here. Before you start Platform Prerequisites Windows Missing paths issue Mac Linux Ubuntu 18.04 Ubuntu 20.04 Oracle Enterprise Linux 7 and Fedora 21 CentOS 8 Common Prerequisites OpenJDK Git Gradle Ant Environment Variables Getting the Sources Using Gradle on The Command Line Build and Test Platform Builds NOTE: cross-build support is currently untested in the mainline jfx-dev/rt repo Customizing the Build Testing Running system tests with Robot Testing with JDK 9 or JDK 10 Integration with OpenJDK Understanding a JDK Modular world in our developer build Adding new packages in a modular world First Step - development Second Step - cleanup Before you start Do you really want to build OpenJFX? We would like you to, but the latest stable build is already available on the JavaFX website, and JavaFX 8 is bundled by default in Oracle JDK 8 (9 and 10 also included JavaFX, but were superseded by 11, which does not). -
Build Prerequisites
Build Prerequisites Table of Contents 1 Overview 2 Introduction 3 IDE 4 Download 5 Installation 5.1 Git for Windows 5.2 TortoiseGit 5.3 YASM (since MP 1.25 Final, YASM is provided as nuget package, you can skip this ) 5.4 NuGet Package Manager 5.5 NSIS 6 Configuration 6.1 .Net Framework 3.5 6.2 Windows and DirectX SDK Environment Variables 6.3 TortoiseGit 7 Next Steps 8 Changelog Overview How to setup your system with the required software to access and use or contribute to the MediaPortal source code, particularly for compiling and building an installer.. Introduction In order to reduce the size of the MediaPortal Git repository and simplify merging branches and testing, C++ sourced binaries have been removed from the repository as of April, 2013. This change affects the way in which you setup your system to compile and build MediaPortal. This guide is written for anyone who wants access to our MediaPortal source code repository to compile and build individual branches for testing or development, using either Windows 7 or Windows 8. Note: You should have already installed the Required software for MediaPortal on the system where you install Git, see Requirements > System Components IDE Our source repository contains Microsoft Visual Studio 2013 solutions. We recommend using Visual Studio 2013 Community Edition but any commercial edition should work too. Download Let's start with downloading the required software: Git for Windows (get the latest Full Installer) TortoiseGit (32bit or 64bit depends on your OS) Visual Studio 2015 Community -
Winframe API SDK Programmer's Guide
WFAPI SDK Programmer's Guide Introduction The Citrix WFAPI functions enable application programs to perform tasks that are unique to XenApp and XenDesktop. Appropriate hotfixes and service packs may be needed for the functions defined here to execute properly. In this document XenApp and XenDesktop will be referred to as Citrix VDA. XenApp (RDS VDA) runs on server OSs, Microsoft Windows 2008R2 (Win 7 server) and Windows 2012R2 (Win 8.1 server) and XenDesktop (WS VDA) runs on workstation OSs, Windows 7, Windows 8.1, Windows 10. This SDK allows software developers to programmatically access features specific to Citrix VDAs. For example: • Enumerating servers, sessions, and processes • Managing servers, sessions, and processes • Accessing Citrix-specific user data • Sending messages to a session • Using virtual channels • Waiting on system events The WFAPI SDK comprises a set of function calls to the Wfapi.dll dynamic link library (DLL) for 32- bit applications and Wfapi64.dll for 64-bit applications. These DLLs are available on servers running XenApp and on Windows Workstation platforms running XenDesktop. Example programs are included to assist developers. Using the WFAPI SDK The WFAPI SDK is intended for use by OEMs and customers who need to write applications that directly call WFAPI functions, using Microsoft Visual C++, Version 12.0 (Visual Studio 2013). System Requirements The WFAPI SDK must be installed and built on a Windows 7, Windows 8.1, Windows 10, Windows Servers 2008R2 or 2012R2 computer with sufficient disk space. The SDK does not need more than a few megabytes of disk space; however, third-party development tools (for example, Microsoft Visual C++) may require a substantial amount of disk space. -
IBM Connect:Direct for Microsoft Windows: Documentation Fixpack 1 (V6.1.0.1)
IBM Connect:Direct for Microsoft Windows 6.1 Documentation IBM This edition applies to Version 5 Release 3 of IBM® Connect:Direct and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 1993, 2018. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. Release Notes.......................................................................................1 Requirements...............................................................................................................................................1 Features and Enhancements....................................................................................................................... 2 Special Considerations................................................................................................................................ 3 Known Restrictions...................................................................................................................................... 4 Restrictions for Connect:Direct for Microsoft Windows........................................................................ 4 Restrictions for Related Software.......................................................................................................... 6 Installation Notes.........................................................................................................................................6 -
A Software-Based Remote Receiver Solution
Martin Ewing, AA6E 28 Wood Rd, Branford, CT 06520; [email protected] A Software-Based Remote Receiver Solution Need to get your receiver off site to avoid interference? Here is how one amateur connected a remote radio to a club station using a mixture of Linux, Windows, and Python. The local interference environment is an station computer would run control software details are available at www.aa6e.net/wiki/ increasing problem for ham radio operation, to manage the remote operation. W1HQ_remote. Hardware construction is making weak signal operation impossible This article focuses mostly on the straightforward for anyone with moderate at some times and frequencies. The ARRL software — how we developed a mixed C experience. Staff Club Station, W1HQ, has this problem and Python (and mixed Linux and Windows) in spades when W1AW, just across the project with audio and Internet aspects. System Overview parking lot, is transmitting bulletins and Interested readers will probably want to Figure 1 shows the overall system design. code practice on seven bands with high consult the code listings. These are provided The BeagleBoard XM or “BBXM” is an power. Operating W1HQ on HF in the prime at www.aa6e.net/wiki/rrx_code and are inexpensive (~$150) single board computer evening hours is not possible. There is no also available for download from the ARRL with a 1 GHz ARM processor, Ethernet problem transmitting in this environment QEX files website.1 Additional project and USB connections, and on-board audio — it’s a receiver problem. We could solve 2 1 capability. It has 512 MB of RAM and the problem by setting up a full remote base Notes appear on page 6. -
Visual Build Help
Visual Build Professional User's Manual Copyright © 1999-2021 Kinook Software, Inc. Contents I Table of Contents Part I Introduction 1 1 Overview ................................................................................................................................... 1 2 Why Visual................................................................................................................................... Build? 1 3 New Features................................................................................................................................... 2 Version 4 .......................................................................................................................................................... 2 Version 5 .......................................................................................................................................................... 3 Version 6 .......................................................................................................................................................... 4 Version 7 .......................................................................................................................................................... 7 Version 8 .......................................................................................................................................................... 9 Version 9 ......................................................................................................................................................... -
Windows Phone API Quickstart
Windows Phone API QuickStart Fundamental Types and Threading and cont. cont. Wallet▲ Date / Time Synchronization .NET Microsoft.Phone.Maps.Controls Microsoft.Devices Map, MapLayer, MapOverlay, .NET Microsoft.Phone.Maps.Services Microsoft.Phone.Tasks Windows Runtime PhotoCamera, CameraButtons, CameraVideo- ♦♣ Windows Runtime + GeocodeQuery, ReverseGeocodeQuery, Route- AddWalletItem Windows.Foundation ♦ BrushExtensions Windows.System.Threading Microsoft.Phone Query Microsoft.Phone.Wallet DateTime, Uri ThreadPool, ThreadPoolTimer Microsoft.Phone.Tasks Wallet, Deal, WalletTransactionItem, WalletAgent ♦♣ ♦ PictureDecoder Windows.Foundation.Collections Windows.UI.Core MapsTask, MapsDirectionsTask, MapDownload- Microsoft.Phone.Tasks ▲ IIterable<T>, IVector <T>, IMap<TK, TV>, IVec- CoreDispatcher, CoreWindow, erTask Multitasking torView <T> MediaPlayerLauncher, CameraCaptureTask, ♦ Note: You can get the current dispatcher from PhotoChooserTask, ShareMediaTask, SaveRing- System.Device.Location Windows.Storage.Streams CoreWindow.GetForCurrentThread() GeoCoordinateWatcher .NET Buffer toneTask Microsoft.Xna.Framework.Audio Microsoft.Phone.BackgroundAudio .NET BackgroundAudioPlayer, AudioTrack, AudioPlay- Microphone, SoundEffect, DynamicSoundEffec- ▲ .NET System tInstance erAgent, AudioStreamingAgent ♦ + VoIP System WindowsRuntimeSystemExtensions Microsoft.Xna.Framework.Media Microsoft.Phone.BackgroundTransfer ■ Object, Byte, Char, Int32, Single, Double, String, System.Threading MediaLibrary, MediaPlayer, Song Windows Runtime BackgroundTransferService, -
Sharepoint Online Custom Solution Resources Applies To: Office 365 Dedicated – Legacy Release
SharePoint Online Custom Solution Resources Applies to: Office 365 Dedicated – Legacy Release Topic Last Modified: 2014-04-07 This section describes resources available to customers and third party providers building custom solutions for SharePoint Online Dedicated. Custom Solutions Resources for SharePoint Online Dedicated The resources available to developers of SharePoint Online custom solutions include: Custom Solution Policies and Process (FTC) This article describes the policies and process that govern how Microsoft and its subscribers to SharePoint Online for enterprises dedicated plans validate and deploy custom solutions to the SharePoint Online environment. SharePoint Online Custom Solution Developer's Guide (Dedicated Plans) This article provides SharePoint Online Dedicated plan customers with guidelines and best practices to help you develop custom solutions that you can deploy to the SharePoint Online environment. Submitting Custom Solutions to SharePoint Online Using MSOCAF This article describes how to use Microsoft SharePoint Online Code Analysis Framework (MSOCAF), which is the tool you use to validate and submit SharePoint Online custom solutions. SharePoint Online Custom Solution Resources Legacy Release Office 365 Dedicated & ITAR-support Plans © 2015 Microsoft Corporation. All rights reserved. Page 1 of 222 Custom Solution Policies and Process (FTC) Topic Last Modified: 2014-04-11 This article describes the policies and process that govern how Microsoft and its subscribers to SharePoint Online Dedicated validate and deploy custom solutions to the SharePoint Online environment. These custom solutions include solutions and products that are developed by third parties and code developed in-house by customers. Custom solutions can be deployed to any web application in the SharePoint Online Dedicated environment (Portal, Team, Partner, or Personal Sites). -
Micro Focus Enterprise Developer 7.0 Build Tools for Windows
Micro Focus Enterprise Developer 7.0 Build Tools for Windows Release Notes Micro Focus The Lawn 22-30 Old Bath Road Newbury, Berkshire RG14 1QN UK http://www.microfocus.com © Copyright 2021 Micro Focus or one of its affiliates. MICRO FOCUS, the Micro Focus logo and Enterprise Developer are trademarks or registered trademarks of Micro Focus or one of its affiliates. All other marks are the property of their respective owners. 2021-07-06 ii Contents Enterprise Developer Build Tools for Windows Release Notes .....................4 Installation .......................................................................................................... 5 Prerequisites for Using Enterprise Developer Build Tools for Windows .............................. 5 Installing Enterprise Developer Build Tools for Windows .................................................... 5 Microsoft Package Dependencies .......................................................................................6 Managing the Microsoft Build Tools and Windows SDK Packages .....................................7 The Microsoft Build Tools and Windows SDK Configuration Utility .......................... 7 Restrictions .......................................................................................................10 Licensing Considerations ............................................................................... 11 Updates and Customer Care ........................................................................... 12 Further Information and Product Support ........................................................................ -
Using the Microsoft Windows SDK Tools to Compile Against Spincore Libraries
Using the Microsoft Windows SDK Tools to Compile Against SpinCore Libraries SpinCore Technologies, Inc. November 19, 2013 1 Introduction Recently, SpinAPI's compilation process has moved to the Microsoft Windows SDK C/C++ compiler. The reason behind this move away from GCC is that true 64bit support became necessary. In order to use GCC for 64bit compilation on Windows, plain MinGW is not enough; a Cygwin environment with a 64bit port of MinGW becomes necessary. Requiring the use of Cygwin not only complicates the compilation process for us, but for customers as well. The current solution to this problem is to use the Microsoft Windows SDK C/C++ compiler. The SDK provides an easy way to setup the correct build environment for 64bit or 32bit, and also will use the correct C++ name mangling conventions for C++ libraries compiled with Visual Studio. Additionally, the compilation method is easily scriptable. 2 Install necessary Tools The Microsoft Windows SDK (at least v7.1 is recommended) is required to compile C programs against the SpinAPI library, or other SpinCore API packages. The Windows SDK can be found for free on Microsoft's MSDN website. 3 Setup Build Environment The Microsoft Windows SDK comes with a tool called \setenv.cmd". This is the tool that is used to setup the 64bit and 32bit build environments. It is found in the installation directory of the SDK under the \Bin" folder. If you would like to have this tool available at the command line without typing out the absolute path, you will need to add the \Bin" directory to the system's path variable. -
C++Builder XE5 Feature Matrix | Multi-Device, True Native App
C++Builder® XE5 Multi-device, true native app development with C++ Feature Matrix Feature Architect Ultimate Enterprise Professional Starter INTEGRATED COMPILERS AND TOOLCHAINS Introduced in XE3! C++ 64-bit compiler for Windows X X X X Enhanced in XE3! C++ OS X compiler X X X X Enhanced in XE5! Embarcadero C++ Compiler 6.70 (bcc64) X X X X Enhanced in XE5! Embarcadero C++ Compiler 6.70 (bcc32) X X X X Enhanced in XE3! C++ command line toolchains for Windows X X X X X Enhanced in XE3! C++ command line toolchains for OS X (bccosx) X X X X Create 32-bit optimized native executables that can run on both 32 X X X X X and 64-bit Windows operating systems Enhanced in XE3! ANSI/ISO C++11 and 99 Standard language X X X X conformance and Boost support for 64-bit #pragma once support that allows for better compatibility with MSVC X X X X X and also acts as a header guard [[deprecated]] attribute to flag constructs as deprecated X X X X X Build C++ packages for 32-bit applications X X X X X Secure C library functions X X X X X Enhanced compiler switches for XML representation of source code X X X X X Custom evaluators for C++ Strings types X X X X X Linker error handling to improve memory management flexibility and X X X X X resolution APPLICATION PLATFORMS, INTEGRATED FRAMEWORKS, DESIGNERS AND SDKS Enhanced in XE3! FM Application Platform for creating 32-bit Windows applications for Windows 8, Windows 7, Windows Vista and X X X X X XP; Server 2008 and 2012. -
Peliohjelmointi Windows Phone 8:Lle
Toni Bäckström Peliohjelmointi Windows Phone 8:lle Metropolia Ammattikorkeakoulu Insinööri (AMK) Tietotekniikka Insinöörityö 21.5.2014 Tiivistelmä Tekijä(t) Toni Bäckström Otsikko Peliohjelmointi Windows Phone 8:lle Sivumäärä 35 sivua Aika 21.5.2014 Tutkinto Insinööri (AMK) Koulutusohjelma Tietotekniikka Suuntautumisvaihtoehto Ohjelmistotekniikka Ohjaaja(t) Lehtori Juha Pekka Kämäri Lehtori Jorma Räty Tässä insinöörityössä tutustutaan Windows Phone 8 -mobiilikäyttöjärjestelmään peliohjelmoijan näkökulmasta. Työn tavoitteena oli erityisesti esitellä Microsoftin itse kehittämiä XNA- ja DirectX-peliohjelmointikirjastoja teoriassa ja käytännössä. Työn aluksi käydään läpi hieman Windows Phonen historiaa ja yleisesti kehittämistä Windows Phone 8:lle. Tämän jälkeen luodaan katsaus Windows Phone 8:aan pelialustana. Työn suurin osuus on XNA:n ja DirectX:n esittely teoriassa; kummastakin menetelmästä käydään läpi grafiikan, äänen ja syötteiden käsittely sekä esitellään tärkeimpiä yleisiä ominaisuuksia. Lisäksi katsotaan molempien menetelmien historiaan ja tulevaisuuteen. XNA:n todetaan olevan DirectX:ää selvästi helpompi ohjelmoida, mutta sen kehityksen loputtua ei XNA:n tulevaisuus ole yhtä turvattu kuin DirectX:n. Työssä esitellään myös apukirjasto DirectX Toolkit, jolla DirectX:n käytöstä saadaan huomattavasti yksinkertaisempaa. Käytännössä XNA:ta ja DirectX:ää tutkitaan kehittämällä pienimuotoinen peli kumpaakin menetelmää käyttäen. Yksinkertaisen 2D-pelin ohjelmoinnissa käytettiin hyvin pitkälti samoja keinoja, jotka teoriaosuudessa oli esitelty.