how i can install compaq visual fortran on windows 7 64-bit?
it is not compatible with win64
No, I don't think so. According to Steve Lionel, of Powerstation/Digital/Compaq/Intel Fortran fame (the man's been at it for some time :) CVF has some trouble running on Win7. Not suprising, since it is a product whose development has been discontinued sometimes about 5 years ago.
My recommendation is that you upgrade to Intel Fortran, which is of the same line, meaning all your libraries (for example, for plotting on screen) will still be there. Their new product recently has introduced more than a few significant changes, and it is well worth it. Runs on VS2010 (full or shell) so you shouldn't have any trouble with it.
Contrary to what has been said, the Compaq Fortran 6 environment can be run within Windows 7 - 64 bits.
Personally, I ran the setupx86.exe file located in the X86 subdirectory of the CVF CD, but I specified that the files should be put into the Program Files (x86) directory. Then when I ran the Developer Studio and tried to compile a Fortran program. It said it did not find some libraries. So, within the CVF environment, I clicked on Tools/Options/Directories and told the program to get library, include,... files from the Program Files (x86) directory.
Then everything worked just swell !
If not, try to use the compatibilty option by right clicking on the Developer Studio icon.
Assuming your copy of Windows 7 is one of the higher end versions that supports it, you can install "Windows XP Mode" (really, a copy of Microsoft's virtual machine) and probably run it under that.
Related
Apologies for the beginner question.
In short I'm trying to compile a very simple C++ program for Linux from Windows 10. A few answers say "install cygwin" but I'm not sure it's the optimal solution. Would it be simpler to just install Linux and build for Linux from Linux and for Windows from Windows, or do cross-compilers already exist that could take care of the work for me?
Thank you
Edit: maybe my question wasn't clear. Essentially, I'm using VSCode on Windows. I have C++ code that I'd like to compile for Linux from Windows. I installed MinGW and it lets me compile Windows executables without issue. However I have no idea on how to compile executables for Linux.
You have several choices:
WSL.
WSL(Windows Subsystem for Linux) its linux termanal in windows, so you can compile linux code in windows. This solution is the simpliest and I would recommend to use it.
Visual studio.
Visual studio has a package that allows you to compile programs for Linux. More details here
The Linux and Windows libraries have some implementation differences. And also have different executables. Windows project may not work on Linux. But you can use the Visual Studio IDE with the Linux Developer Extension. Or can use WSL (Linux terminal for Windows) with Visual Studio Code (just install correct extension).
Compiling a very simple C++ program for Linux from Windows 10 can be done on a vanilla Windows 10 system by installing an Arm-provided, mingw32, toolchain:
Aarch32/Arm 32 bit:
gcc-arm-10.3-2021.07-mingw-w64-i686-arm-none-linux-gnueabihf
Aarch64/Arm 64 bit:
gcc-arm-10.3-2021.07-mingw-w64-i686-aarch64-none-linux-gnu
I'm sorry, I didn't quite understand the question. But when I start linux and try to make a C++ program. I started by trying to install the compiler through the terminal, then made a simple C++ program, and it worked. To begin with I visited this site :
https://linuxconfig.org/how-to-install-g-the-c-compiler-on-ubuntu-18-04-bionic-beaver-linux
Hopefully can help
I would like to be able to compile C and C++ code under the Windows environment without using an IDE, just by using the Windows Command prompt (cmd.exe).
I come from Linux, where you are be able to install the gcc package with just a command in the terminal:
$ sudo apt install gcc
I wonder if there is a C/C++ compiler collection in a package inside the Windows install folders, just like the ones in Linux, I just need to install.
What also gives me a reason to ask this question is:
Since the kernel of Windows and the Windows API are written in C, and many of the high-level applications of the actual Windows 10 release are written in C++, it would be reasonable to also directly provide a suitable compiler suite. This is my thought modell, does not need to match reality.
Thanks for your help.
Since the kernel of Windows and the Windows API are written in C
Microsoft doesn't ship a compiler, or the required Windows SDK headers/libs (also includes a bunch of other useful development tools) for Windows in the installation.
Microsoft Visual C++ (part of Visual Studio) would be the equivalent "built in" choice although I am not sure if Microsoft ever specify exactly which version they use for a given Windows build and it is common to have lots of software built with different compilers/versions (including the various non-Microsoft ones).
As well as the full Visual Studio package with the IDE and other tools. Microsoft provide some components separately, such as the Build Tools for Visual Studio 2019.
I am sure this is for many reasons like most users not being interested in compiling their own software, and Microsoft still sells Visual Studio separately to larger organisations (historically to most serious users, but "Community" edition is now pretty nonrestrictive for individuals and small business).
Strangely enough it doesn't come with a C compiler, we need to install one, Mingw-w64 is allways my choice, you will need to add the path in environment variables (step 12), if you want to use it anywhere. You can then use the gcc command where it's more convenient like in Linux, don't forget to open a new cmd after the changes for them to take effect.
Unfortunately, Windows doesn't have the command line tools for installing/removing stuff and the great repository infrastructure we know and love from Linux.
You will need two things:
The command-line build tools. These can be found on the Visual Studio Downloads page under Tools for Visual Studio -> Build Tools for Visual Studio. This will include the compiler (cl.exe) and linker (link.exe) for the MSVC build toolchain.
The Windows SDK. The latest version of the SDK can currently be found here. This page has a tendency to move around, but googling for Windows SDK usually gives you the right page immediately. The SDK contains all the headers and libraries required to build Windows applications and make use of the Windows native API. The Windows SDK contains a lot of stuff which you may or may not need. You will almost certainly want to install the Windows SDK for Desktop C++ x86 Apps and Windows SDK for Desktop C++ amd64 Apps components. Most of the other stuff should be optional, but some of it is nonetheless highly useful.
You may want to download additional packages such as the Windows Debugger (which is an entirely different application than the Visual Studio debugger) or the Driver SDK, depending on what kind of things you want to develop.
Note that even if you don't intend to use the IDE in the end, installing the full Community Edition of Visual Studio is a far more convenient way to get a working build environment, so unless you have a really good reason not to, just go with the full package and choose to never open the IDE.
The built in compilers available on Windows 10 are for VisualBasic, C#, JScript.
To improve speed & performance of apps, "ngen.exe creates native images, which are files containing compiled processor-specific machine code, and installs them into the native image cache on the local computer. The runtime can use native images from the cache instead of using the just-in-time (JIT) compiler to compile the original assembly".
For low level programmers, ilasm.exe (IL Assembler) ships with Windows, which also facilitates "tool and compiler" development; so you could even create your own language or build a better compiler for a current one, or "debug your code at low level and understand how .NET deals with your high level code", or "write your own compiler for a new .NET language."
For web programmers, AspNetCompiler precompiles server-side ASP.NET web-applications, therefore helps application performance because end users do not encounter a delay on the first request to the application.
All Compilers & assemblers come as builtin with Windows without IDE and can be run from "the Windows Command prompt (cmd.exe)", so no extra downloads necessary; located in folder: C:\Windows\Microsoft.NET\Framework\vx.x.xxxxx\ .
Note: C# is based on JScript.
Compilers:
vbc.exe
csc.exe
jsc.exe
ilasm.exe
ngen.exe
aspnet_compiler.exe
Addendum:
If you still are looking for a C compiler to handle some C source codes you already have spent your life on, then (without downloading) you can make/write a C compiler, in a high level language, then optimize it with a low level language.
This guide will "introduce you to the high-level architecture, theory, and .NET Framework APIs that are required to build your own .NET compiler" in C#.
You can to use gcc for windows. For e.g. mingw, tdm-gcc, mingw-68, Cygwin etc. Each of them allows you to work on c/c++. But if you are not sure about the installation process, and don't want to do all the work by yourself, the easiest solution is to download something like dev-c++ or code-blocks.
cygwin: https://cygwin.com/
mingw-64: http://mingw-w64.org/doku.php
Downloadable file can be found here (for mingw, dev-c++): https://sourceforge.net/
You can also install Microsoft compiler. I usually do it by installing the whole visual studio.
i write a code and in this code i use graphics.h ,in borland c++ or visual I can't open and run it, now i want run this code ,and i have DOSBOX 0.72 , how open this code with DOSBOX?
my windows is 7 32bit
I see you're still trying to write and compile code that uses legacy and unsupported libraries...
At least you've discovered now that you aren't going to be able to do this natively in Windows 7, and have installed a DOS emulator. Now, you'll need to find and download a compiler that will run in that environment.
Since graphics.h is a proprietary Borland library, I recommend you use one of their compilers. The company who now owns Borland hosts an online museum of their vintage products that are free for download. Grab a copy of Turbo C 2.01 or Turbo C++ 1.01, load it on your DOSBOX, and marvel at the little piece of computer history you've unearthed.
Also, Turbo C 3.0 is available online from here, but I'm not sure this has been released to the public domain. I can't imagine anyone would really care, but legally and all, you're on your own.
But seriously, why not download Visual Studio C++ 2010 Express free from Microsoft and use a modern compiler instead? Sure you can't use graphics.h, but there have been a significant amount of developments made in computer graphics technology in the past 25+ years. A modern IDE will be much easier to use than the old Borland compilers, and the time you invest will actually be worth something.
May be download and install borland c++ 3.11 compiler and use graphic.h library (i'm use it 4 years ago).
I think that this compiler isn't ran in Win 7, but may be try.
You can use Virtual Box, with installing Win XP (borland c++ 3.1 100% work in WinXP).
The complete solution of running turbo C++ 3.0 in windows 7 is just disable graphics driver of your computer from device manager and use like windows Xp.
It will run turbo c++ in full screen as well as run graphics program in windows 7
how do i turn my VC++ 2008 program into something i can get to run on other computers. i have tryed using the .exe it makes in the debug but it will say that im missing some files and lists all of my .cpp file names and .h files(if i use it on other computers). i wanted something so i could encrypt my files because one of them is about encrypting passwords/other stuff so i can't have someone just open my files. also i would very much like someway to make them accept the terms and conditions so they can't sue me if they lose something, that would be very very nice. ^^
i only have Microsoft virtual c++ 2008 express edition that i got from their web site.
o also if i make something on windows 7 will it run in xp or vista?
You generally can't and almost never should distribute debug builds to client machines. At least three reasons.
Client machines will not have the debug versions of your dependant libraries, like the VC runtime (msvcrtd.dll), so they won't be able to run your app.
When compiling in debug, your code will in many ways run unoptimized. For one thing, you don't let an optimizing compiler optimize when you compile in debug, so it will run slower and/or fatter. For another, there are debug version of things like operator new which allocate much more than you ask for, which is used in runtime integrity checking etc. So your program runs fatter & slower once more.
When you compile in debug it is easier to reverse-engineer your code.
UPDATE:
And to answer your question if a Win7-compiled app will run on XP/Vista, the answer is 'yes' so long as you don't use any Win7 features.
You will need the redist pack for the binary to run on another machine (if it does not already have the pack installed).
You need to make a Deployment Project that generates an MSI, but I'm not sure your Express edition does that. As for encryption, compilation doesn't do that, and nothing stops people from disassembling your code. Finally, you probably should not be writing your own encryption algorithms, since most people get those wrong most of the time. Use something out of the box.
if you are compiling using .NET 3.5 in Win 7 it should work in xp and vista as well
(provided .NET 3.5 framework is installed on them).
The first part is already answered (release build, include redistributable C++ DLLs).
The second part, running on Vista/XP is not that trivial.
If you write a pure C++ program, it will run on XP and Vista, unconditionally. But once you include <windows.h>, you introduce a dependency on a minimum Windows version. The default today is still XP. That means that you cannot use any Vista or W7 feature directly, and therefore your program can run on XP.
But if you #define WINVER 0x0600 before including <windows.h>, then you can use Vista-specific functions. The price you pay for using those Vista functions is that your program won't start on XP anymore. Similarly, #define WINVER 0x0601 also gives you access to Windows 7 functions, on top of the XP and Vista functions. And again, using a Windows 7 function stops you from running on XP or Vista.
There are some tricks that allow you to use Windows 7 functions if available. Basically, they all boil down to calling GetProcAddress("some_windows7_function") and somehow handling the case where it returns NULL.
I'm using Code::Blocks with MinGW to write my C++ applications in Windows XP.
Now I want to compile my code to run under an MS DOS environment, so I can put it on my DOS formatted floppy disc. Can anyone help me?
Thanks in advance.
P.S. I don't mean the Command Prompt, but really the good old MS DOS Operating System.
It's pretty old, but DJGPP exists precisely for DOS development. I hasn't been updated since 2000, but it works.
It's basically the same as MinGW, but exclusively for DOS.
What year was this written??? (Says four months ago.) Uh, no, DJGPP is still supported, it has G++ 4.4.1 (or unofficial 4.4.2, even)!! The libc itself is still being (very slowly) tweaked, but even 2.03p2 "stable" is from 2002 and 2.04 "beta" from 2003. Where did you get year 2000 and GCC 2.96 (never supported by DJGPP, 2.96 wasn't even an official FSF release, it was a Red Hat fork) from????
I have a setup for developing MSDOS programs from Windows 10 (or whatever Windows you want basically), using the Code::Blocks IDE, and the Open Watcom v2 or Digital Mars C/C++ compilers. Code::Blocks has support for these compilers built into it, but the settings will need a bit of tweaking to get it to build correctly for DOS.
OpenWatcomv2
Open Watcom is the easiest to setup with Code::Blocks. Basically, install Open Watcom following the installation instructions on it's site. Then open Code::Blocks and open "settings"->"compiler" select the "Open Watcom (W32) Compiler", go to "toolchain executables" and direct it to the correct executables and directories of Open Watcom.
C/C++ compiler: wcl.exe
Dynamic libs: wlink.exe
Static libs: wlib.exe
Resource compiler: wrc.exe
Make program: wmake.exe
In the "additional paths", make sure you put
"[OpenWatcomDir]/binnt"
"[OpenWatcomDir]/binnt64"
...assuming you want to use the 64 bit version, see installation instructions otherwise
Also, you will need to go to the "Compiler Options" tab, and right click->modify the option "compile and link for DOS" under the "Executable type options section". You need to add "system dos" in the "linker flags" box, then hit "OK."
I believe this is all you need to do in order to start building DOS programs. Just setup a project with the desired compiler options (memory model and such) and you are good to go. You will need an emulator of some kind to test them without booting DOS or something. I recommend 86Box for testing, as it is a very accurate emulator.
I haven't developed for MS-DOS for some decades; but I'd start checking the tools used on Free-DOS. Maybe there's already a gcc package for it.