SubInACL is a commandline tool that enables administrators to obtain security information about files, registry keys, and services, and transfer this. PGI Products Which releases of PGI compilers work with each Linux distribution on x. Each release of Linux changes many things, primarily the glibc libraries, the locations of files and headers for gcc, and changes to how executables are built. As a result, the PGI compiler install process has to adjust with each release, and the code shipped needs to be updated or expanded. Most compiler releases will be compatible with previous Linux versions existing at that time, and we make an effort to be compatible with future releases, by trying to use the most current versions of libraries and headers from the installation for unfamiliar releases. Here are the PGI compiler releases and the distributions of Linux x. Note, as is commonly done, we only update the most current release for a new distribution of Linux. The Linux distribtuion involved comes with a specific glibc and gcc version. If you use the versions that are bundled as part of the development tools for that Linux release, and they match another supported release below, then your installation will probably succeed. HPC servers are quickly expanding beyond multicore x86 CPUs to OpenPOWER, ARM and GPU accelerators. PGI Fortran, C and C compilers and OpenACC are designed to. Not all versions of gccglibc can work with any Linux releasekernel, however, so any custom combination of Linux with gcc tools and libs should not be too different from the bundled release. Here is a table of the Releases available and how to bring them up to their most up to date version. Be sure to add any patches after the latest version is downloaded and installed. Release Linux x. 86 6. Releases Verified to Install Newest Version Notes 2. RHEL 5. 37. 3, SLES 1. SP2, open. SUSE 1. Leap 4. 2. 2, Fedora 1. Cent. OS 5. 1. 17. Ubuntu 1. 0. 0. 41. Artogon Games. Release version info 2. RHEL 5. 37. 2, SUSE 1. SLES 1. 11. 2 SP1, open. SUSE 1. 1. 1Leap 4. Fedora 1. 02. 3, Cent. OS 5. 1. 17. 1, Ubuntu 1. Release version info 2. Red Hat 9. 0, and RHEL 4. SUSE 9. 31. 1. 2,SLES 1. SP3, open. SUSE 1. Fedora 42. 1, Cent. OS 5. 27, Ubuntu 8. Release version info 2. Red Hat 9. 0, and RHEL 4. SUSE 9. 09. 19. SLES 91. SP1 SP2, open. SUSE 1. Fedora 42. Cent. OS 6. Ubuntu 899. Release version info 2. Red Hat 9. 0, and RHEL 4. SUSE 9. 09. 19. SLES 91. SP1 SP2, open. SUSE 1. Fedora 41. Ubuntu 899. Release version info 2. Red Hat 9. 0, and RHEL 4. Su. SE 9. 09. 19. SLES 91. 01. 1 SP1, Fedora 41. Ubuntu 899. 0. 41. Release version info 2. Red Hat 9. 0, and RHEL 4. Su. SE 9. 09. 19. SLES 91. 01. 1, Fedora 4567891. Ubuntu 899. 0. 41. Release version info 2. Red Hat 9. 0, and RHEL 4. Su. SE 9. 09. 19. Creation Master Fifa 09 Download For Pc there. SLES 91. 01. 1, Fedora 4567891. Ubuntu 899. 0. 4 1. Release version info 9. Red Hat 9. 0, and RHEL 3. Su. SE 9. 09. 19. SLES 91. 01. 1, Fedora 4567891. Ubuntu 89 6. 4 bit SLES 91. Su. SE 9. 09. 19. RHEL 3. 04. 05. Fedora 4567891. Ubuntu 89 9. 0 4 Release info 8. Red Hat 9. 0, and RHEL 3. Su. SE 9. 09. 19. SLES 91. 01. 1, Fedora 456789, Ubuntu 8 6. SLES 91. 01. 1, Su. SE 9. 09. 19. 29. RHEL 3. 04. 05. Fedora 456789, Ubuntu 8 8. Release info 7. 2 3. Red Hat 9. 0, and RHEL 3. Su. SE 9. 09. 19. SLES 91. 0, Fedora Core 45678 6. SLES 91. 0, Su. SE 9. RHEL 3. 04. 05. Fedora Core 45678 7. Release info Which releases of PGI compilers work with each Linux distribution on Open. POWER Release Linux Open. POWER Releases Verified to Install Newest Version Notes 2. Ubuntu 1. 4. 0. 4 1. RHEL 7. 3 7. 4 POWER9. Release version info Which releases of PGI compilers work with each Windows version PGI Professional Edition for Windows. Versions are added as they become available. Release Windows Versions Verified to Install Newest Version Notes 2. Server 2. 00. 8 R2Server 2. Server 2. 01. 61. Release version info 2. Server 2. 00. 8 R2Server 2. Release version info 2. Server 2. 00. 8 R2Server 2. Release version info 2. XPVista788. 1Server 2. Server 2. 00. 8Server 2. XP x. 64Vista788. Server 2. 00. 3 x. Server 2. 00. 8 R2Server 2. Release version info 2. XPVista78Server 2. Server 2. 00. 8Server 2. XP x. 64Vista78Server 2. Server 2. 00. 8 R2Server 2. Release version info 2. XPVista7Server 2. XP x. 64Vista7Server 2. Compute Cluster ServerHPC Server 2. R2 1. 2. 1. 0 Release version info 2. XPVista7Server 2. XP x. 64VistaServer 2. Compute Cluster ServerHPC Server 2. R2 1. 1. 1. 0 Release version info 2. XPVista7Server 2. XP x. 64VistaServer 2. Compute Cluster ServerHPC Server 2. Release version info 9. XPVistaServer 2. XP x. VistaServer 2. Compute Cluster ServerHPC Server 2. Release info 8. 0 3. XPVistaServer 2. XP x. VistaServer 2. Compute Cluster ServerHPC Server 2. Release info 7. 2 3. XP x. 64VistaServer 2. Compute Cluster Server 7. Release info ote on Windows 7 compatibility FLEXlm versions delivered with PGI 2. PGI 2. 01. 1 releases were compatible with only the 3. Windows 7. PGI 2. Windows 7. Which releases of PGI Visual Fortran compilers work with each Windows version Versions are added as they become available. Note PVF is NOT compatible with Visual Studio Express. PVF will not install or run successfully on systems with VS Express present regardless of the VS Express version or PVF version. Release Windows Versions Verified to Install Newest Version Notes 2. Server 2. 00. 8 R2Server 2. Server 2. 01. 6 Supports Microsoft Visual Studio 2. VS 2. 01. 5 shell included, 2. Release version info 2. Server 2. 00. 8 R2Server 2. Supports Microsoft Visual Studio 2. VS 2. 01. 5 shell included, 2. Release version info 2. Server 2. 00. 8 R2Server 2. Supports Microsoft Visual Studio 2. VS 2. 01. 3 shell included, 2. Release version info 2. XPVista788. 1Server 2. HPC Server 2. 00. R2Server 2. 01. 2 6. XP x. 64Vista78Server 2. HPC Server 2. 00. R2Server 2. 01. 2 Supports Microsoft Visual Studio 2. VS 2. 01. 3 shell included, 2. Release version info 2. XPVista78Server 2. XP x. 64Vista78Server 2. Compute Cluster ServerHPC Server 2. R2 Supports Microsoft Visual Studio 2. VS 2. 01. 2 shell included, 2. Release version info 2. XPVista7Server 2. XP x. 64Server 2. Compute Cluster ServerVista7HPC Server 2. R2. Supports Microsoft Visual Studio 2. VS 2. 01. 0 shell included and 2. Release version info 2. XPVista7Server 2. XP x. 64Server 2. Compute Cluster ServerVistaHPC Server 2. R2 Supports Microsoft Visual Studio 2. VS 2. 01. 0 shell included and 2. Release version info 2. XPVista7Server 2. XP x. 64Server 2. Compute Cluster ServerVistaHPC Server 2. Supports Microsoft Visual Studio 2. VS 2. 00. 8 shell included and 2. Release version info 9. XPVistaServer 2. XP x. Server 2. Compute Cluster ServerVistaHPC Server 2. Supports Microsoft Visual Studio 2. VS 2. 00. 8 shell included and 2. Release info 8. 0 3. XPVistaServer 2. XP x. Server 2. Compute Cluster ServerVistaHPC Server 2. Supports Microsoft Visual Studio 2. VS 2. 00. 8 shell included and 2. Release info 7. 2 3. XPVistaServer 2. XP x. Server 2. Compute Cluster ServerVista Supports Microsoft Visual Studio 2. Release info. See the note above on Windows 7 compatibility. Can I install PVF on a platform with Visual Studio Express installed No. PVF will not install and run successfully on a system with Visual Studio Express installed. Even installing PVF with the VS 2. VS Express 2. 00. You must first remove VS Express before installing PVF. Which releases of PGI compilers work with each mac. OS version on Intel based Macs PGI products for mac. Developing for Android in Visual Studio gavpugh. DISCLAIMER I tend to waffle on a bit. Skip to the end if you just want to find out about vs android, and where to download it. About six weeks ago I moved into that club which everyone else seemed to be part of, but not me. I joined the ranks of smartphone owners No more 9. I picked up a recent ish Android handset. Id never really been too into the whole concept of smartphone, but was starting to feel a little left behind. I must say that after those few weeks Im sold, these things are pretty cool. So, whats a programmer to doI think I may have actually downloaded the Android SDK before I even received the phone. Yeah, just a little bit eager Its actually the second handheld device Ive tried to code on. The first being the Tapwave Zodiac, also with an arm processor and touchscreen. I never really got anything worthwhile going on it, my excuse being a job hunt and subsequent move to the United States. But nonetheless, it was a fun little handheld to code for. I was certainly looking forward to coding on a much more popular device. Total Eclipse of the IDENow if youve ever tried to write anything for the Android, youll know the preferred development environment is Eclipse. If youre writing your stuff completely in Java, you have everything youd ever need in Eclipse. It seems to do all the nice syntax highlighting, and intellisense like functionality that Visual Studio offers. Of course the shortcut keys are completely wrong, and must have been setup by a madman, but it does seem a pretty good IDE to develop in. Better yet, its freeBut is it for me Nah. Its not for me. I just couldnt get on with it. Primarily I want to write my code in CC too. So I started to convince myself that I neednt bother with Eclipse. I can get all the highlighting and quick reference stuff in Visual Studio, and I could run batch files to build my code. After all, with C under Eclipse you still have to install Cygwin and effectively build from the command line. Visual Studio. Ive used Visual Studio for a very long time now, since its older guise as simply Visual C. Was version 4. 0 I think that I started with, when I moved from DOS to Windows programming. Now its my primary coding IDE Ive used it at both games companies Ive worked at in the past decade. Its an odd one to admit, but its too hard to let the thing go. Makefile Project. So I set off and started a Makefile Project in Visual Studio. I could update the system include paths under Visual Studio 2. I think was trickier with earlier versions, or at least not set on a per project basis, I forget. This meant Id get properly working intellisense of the Android NDK headers, the External Dependencies list in my solution was all completely correct too. All in all, a pretty nice setup. I put together a batch file, which invoked a cygwin session running ndk build. I then setup some further ones which would build the entire package using ant, and then install and run the application on the Android device connected to my PC. Not much to argue with here. For someone who was longing for Visual Studio back, after a few days with Eclipse. It was lovely. If you want to try the makefile method, take a look at this website His method is a little cleaner than the one I used, my batchscript files were hard coded messes of experimentation. Check out the debugging article on his page too, hes got a way of using Win. GDB to debug Android NDK code in Visual Studio. Its awesome. What about when it gets big Unfortunately Androids NDK build scripts under Cygwin on Windows, isnt exactly the performer. When your file count gets into triple figures the initial dependency checks take an age. I also wasnt too enamored with not knowing what was passed to my compiler. You get a limited set of proprietary settings you can change in your makefile, but it did feel like a black box. Coming from a console background, I like to know what my debug and release builds actually are. I also like to setup further build variants too Usually one specific to profiling the game, essentially release with some limited modules enabled to do the profiling. The other major one would be a variant of my debug build, with asserts on but the optimization cranked up to max. So it did feel a little confining. My realization about the build slowdowns with lots of files came when I attempted to integrate third party code Specifically what Im wanting to use is the Irrlicht engine. Its a well structured open source rendering engine. Very versatile, and runs on a variety of platforms. Android included, of course. Runing ndk build, the thing would sit there for well over a minute before even starting to compile files. Ive a recent i. 7 based laptop too, so its no slouch. I had an itching to try and delve into a more integrated method of building with Visual Studio, and that tipped the balance for me. Enter MSBuild. With Visual Studio 2. Microsoft made a radical change to the way their C environment worked. They moved over the entire thing to use MSBuild. Having worked with a certain non Microsoft gaming console, you could see that they had to do a little hoop jumping in previous versions of Visual Studio. Integrating custom compilers with the older versions really appeared to be quite a task. With VS2. 01. 0, it had been hinted on some preview posts from Microsoft that this would be far easier. Unfortunately though when I started to look into this, I found next to no information on the web about it. Well, really I found absolutely nothing in the end. I found a couple of questions on stackoverflow. I ended up searching through the Visual Studio directories to find the existing scripts for Microsofts compiler. From there I duplicated the directory layout and began tinkering with setting up a new platform. Id never used MSBuild before this. It was completely new to me, never even seen a MSBuild file before. Mi Disc View 3.1 Advanced Viewer. I hear some game companies use it, but ours certainly doesnt. I can definitely recommend it though, its very powerful and flexible. It does have quite a learning curve, and Google searching for documentation can lead you to very bad explanations of how it works. If youre at all interested in it, I recommend this book As well as being a very good guide to MSBuild, it actually had a small chapter about exactly what I was trying to do Something I couldnt find at all with Google. Unfortunately I picked the book up after Id done the majority of my scripting, but it at least showed me I was barking up the right tree. So, vs android. Once Id gotten all the features I wanted, and all the bugs I could find ironed out, I decided to release it as open source. The regular download package just consists of a collection of MSBuild scripts, which need to be copied within a certain sub directory of your Visual Studio installation. Alongside the scripts is a single DLL file. When youre working with MSBuild, you can code up custom tasks in a. NET language, such as C. The header dependency scanning code lives here, which invokes gcc to find all the headers that the ccpp files would be dependent on. As well as some other command line switch manipulation code. The full source to the C DLL is up on my Google code page. You can download vs android here Theres full documentation on those pages too. Along with a step by step example of getting Androids san angeles sample app compiling and linking.