I need to document my verilog code using Doxygen. I've installed doxygen version 1.8.10 and doxverilog version 2.6. Moreover, I've xilinx 12.0 and microsoft visual studio 2010 for windows 64 bit. I've followed the following steps and need guidance more as I'm very new to this Doxygen software.
Copy the Verilog files verilogparser.y verlogscanner.l and the others source files from "C:\Doxverilog2.7\sources" to the "C:\doxygen-1.8.10\src".
Copy the patch file "windows.patch" from "C:\Doxverilog2.7\sources" to the "C:\doxygen-1.8.10".
The next step is mentioned in the "ReadMe" file of "Doxverilog2.7" as:
open a shell in the doxygen-1.8.1 directory
make patch # patch -F3 -p1 < windows.patch
but how do I open it? and what is meant by this shell? From where I can get it?
The next step is provided as"Open doxygen-1.8.1\winbuild\Doxygen.vcproj with Visual C++ 2008 Express Edition" but when I build this project in Visual Studio 2010 then it gives me several errors and it is not successfully built. Is there any such project that can be run on visual studio 2010 instead of visual studio 2008?
Also, I want to use Doxywizard so, do I need to follow these steps? Please help me out of this problem.
Thank-you.
Related
I've put Visual Studio Code on OneDrive, for the purpose of syncing it with its settings across my devices.
However, extensions are stored in %USERPROFILE%\.vscode\extensions on Windows.
Is it possible to change this folder's location so I can put it in the main Visual Studio Code folder?
At first I thought that copying the extensions in the resources\app\extensions of Visual Studio Code folder will be a nice workaround, but that doesn't work.
I've also searched for a solution on the documentation page and in the user settings, with no results.
What I did - after installing Visual Studio Code for the first time, I checked the documentation and added at the end of 'Target' field of editor's shortcut the following (there's a space before the two dashes):
--extensions-dir="DRIVELETTER:\VSCODE\extensions"
--user-data-dir="DRIVELETTER:\VSCODE\settings"
where DRIVERLETTER and VSCODE are the corresponding drive and directory where Visual Studio Code is installed. So mine looks like this:
"D:\Microsoft VS Code\Code.exe" --extensions-dir="D:\Microsoft VS Code\extensions"
Here is for the user data directory:
"D:\Microsoft VS Code\Code.exe" --user-data-dir="D:\Microsoft VS Code\settings"
Accessing the 'Target' field is done by right-clicking the shortcut and choosing 'Properties'
Anyway, there's a simpler solution to that problem - just use the portable version of Visual Studio Code. It works under Windows, Linux, and macOS:
Enable Portable Mode
Windows and Linux
After unzipping the Visual Studio Code download, simply create a data folder within Visual Studio Code's folder:
|- VSCode-win32-x64-1.25.0-insider
| |- Code.exe (or code executable)
| |- data
| |- ...
From then on, that folder will be used to contain all Visual Studio Code data, including session state, preferences, extensions, etc.
The data folder can be moved to other Visual Studio Code installations. This is useful for updating your portable Visual Studio Code version: simply move the data folder to a newer extracted version of Visual Studio Code.
macOS
On macOS, you need to place the data folder as a sibling of the application itself. Since the folder will be alongside the application, you need to name it specifically so that Code can find it. The default folder name is code-portable-data:
|- Visual Studio Code.app
|- code-portable-data
Portable mode won't work if your application is in quarantine, which happens by default if you just downloaded Visual Studio Code. Make sure you remove the quarantine attribute, if portable mode doesn't seem to work:
xattr -dr com.apple.quarantine Visual\ Studio\ Code.app
Note: On Insiders, the folder should be named code-insiders-portable-data.
UPDATE 14.12.2021
From Visual Studio Docs
Note: Do not attempt to configure portable mode on an installation from the Windows User or System installers. Portable mode is only supported on the Windows ZIP (.zip) archive. Note as well that the Windows ZIP archive does not support auto update.
A little hack:
Create a symbolic link to the folder %USERPROFILE%\.vscode\extensions under the Visual Studio Code install path.
https://code.visualstudio.com/docs/editor/extension-gallery
code --extensions-dir 'new_directory_to_set'
Set the root path for extensions.
Follow the below steps for changing the extension path in VS.
Set "code" path in environment variable.
path = VS_CODE_INSTALL_DIRECTORY/bin;
Open VS , in VS terminal execute the below command.
code --extensions-dir "new_directory_path"
Install the required extension.
All Done.
Note:Dont forget to vote the answer
According to this page, after installing VS Code we should make a language profilers folder like this:
mkdir code_profiles
cd code_profiles
mkdir code-ruby
cd code-ruby
mkdir exts
mkdir data
For Windows, I prepared a batch file (.bat) for each language I work on, it contains this line:
Start "" "D:\programs\VSCode\code.exe" --extensions-dir D:\programs\VSCode\code_profiles\code-python\exts --user-data-dir D:\programs\VSCode\code_profiles\code-python\data .
This is for Python. If I work on PHP, I will make code-php folder, then make exts and data folders in it and prepare another batch file for PHP, just like the one I made for python.
I put this batch file on the main project folder then double click on it to run VS Code with the preferred profile.
Recently I upgraded a project to Visual Studio 2022. I am using command line to build the installer project (.vdproj) using the command something shown below
devenv.com <Solutionfile> /build <InstallerConfiguration>.
The command used to build file with VS 2019 but when trying to build the same with Visual Studio 2022 seems to be stuck. It seems that everything builds fine but the Visual Studio process does not exit after the project is built and causes the build pipeline to be stalled. I have disabled out of proc build to see if this was causing the issue but it does not help. Any one experience the same issue? I am using the most recent version of visual studio along with the Visual Studio installer project extension. Any other method of building the installer project? I have tried MSBuild command but it does not understand vdproj files.
This has been fixed with the latest release of VS 2022 17.3.6. Works fine for me now.
I'm using Visual Studio 2017. Below is the output from a Visual Studio Developer command prompt indicating the C++ version.
C:\ProgramsNotInstalled\OpenDDS-3.13>cl /?
Microsoft (R) C/C++ Optimizing Compiler Version 19.16.27024.1 for x86
Following that, I see the following output when running the configure --java command.
**********************************************************************
** Visual Studio 2017 Developer Command Prompt v15.9.3
** Copyright (c) 2017 Microsoft Corporation
**********************************************************************
C:\ProgramsNotInstalled\OpenDDS-3.13>configure
ERROR: Could not detect Visual C++ version, try running this script from the Visual Studio Command Prompt.
Stopped at configure line 421.
C:\ProgramsNotInstalled\OpenDDS-3.13>configure --java
ERROR: Could not detect Visual C++ version, try running this script from the Visual Studio Command Prompt.
Stopped at configure line 421.
C:\ProgramsNotInstalled\OpenDDS-3.13>
I saw a similar question posed for DDS 3.12 on stack overflow but that answer has to do with language. That is clearly not the problem in my case, and I am running the configure script from the correct type of command prompt. This question is not a duplicate.
How to install OpenDDS 3.12 on windows system
Evidently, the configure script cannot always detect the compiler version automatically. I'm not good at reading perl scripts because I don't know perl well, but I found an option to help the script.
First determine the exact version of the C++ compiler by running this line:
cl /?
Now using the output of that, add the --compiler option to the command line.
configure --compiler=19.16.27024.1 --java
The instructions within the INSTALL file and README were not clear on that point. I ran configure --help to look at the command line options and that is how I learned that the script will try to autodetect the compiler. My guess is that the script is looking for a specific C++ compiler version or it is using a regex that isn't working well.
This is a small issue in the configure script of OpenDDS 3.13 which is caused by a change in the compiler version which was not known at release time. When you would pull github master (see https://github.com/objectcomputing/OpenDDS) this should work again, or wait until OpenDDS 3.14.
As mentioned here I've tried to build the QGIS on Windows 7.
There are two methods one using Visual Studio Express Edition installer and the second one using MinGW.
I've found both of them broken and don't know what to do next
In building using Visual Studio
The link to visual studio actually installs the version 2010 but documentation assumes it version 2009. So "set VS90COMNTOOLS=%PROGRAMFILES%\Microsoft Visual Studio 9.0\Common7\Tools\" path is not found.
Also I'm confused about the context of this line:
If the path to bison and flex contains blanks, you need to use the
short name for the directory (i.e. C:\Program Files should be
rewritten to C:\Progra~n, where n is the number as shown in `dir /x
C:``).
In Building using MinGW 4.2.1. MSYS link is not found(404) but when I try to build step by step I find XDR 4.0 not found(404) in this page
So what's the way to build it?
All I want is to change the title and startup photo of QGIS Desktop software.
Using another application I'm now able to change the title of running QGIS but don't know where to change the photo which shows "Loading plugins...".
The build instructions for Windows 7 are a tad long in the tooth, but they work for the most part. I did not try MinGW.
I immediately changed the VS90COMNTOOLS path to point to the Visual Studio 2010 directory and it seemed to work for me:
set VS90COMNTOOLS=%PROGRAMFILES%\Microsoft Visual Studio 10.0\Common7\Tools\
Regarding bison and flex configuration, I used the latest version of CMake (3.3.1 as of now) and didn't encounter any warnings/errors pertaining to bison or flex. Are you encountering any right now? If not, you should be able to proceed.
I have a perl script that locates a Visual C install on a machine. It works on a colleagues machine. It fails on my machine. I think it is because I have a different version of Visual Studio and it is installed in a different location.
Here is where I think it is failing
$needpath = 1;
$path = $ENV{"PATH"};
if(grep(/VC/, $path)) {
print "Found Visual C on path\n";
$needpath = 0;
}
Q1. Can someone explain what $ENV{"PATH"}; is? The grep function says it is a LIST. A LIST of what?
Q2. My VS location is “C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\” Why can’t this script find it?
I’ve never used perl before. Please be kind! Thanks.
$ENV{"PATH"} is perl PATH environment variable. In your example grep filters list which size equals one, so same effect could be issued by
if ($path =~ /VC/) { .. }
It seems that your VS is not in the path, which can be checked from command line by set path
I have VS 2010 and VS 2013 installed on my machine.
Have nothing in my path and I believe that visual studio works with relative path.
I think you need something similar like this to look at the installed software.
Visual Studio does not update the PATH for a normal install. There are several command-line toolsets available in Visual Studio versions and some computers have two or more versions installed. These would lead to issues of which version should be placed in the PATH. To avoid this Visual Studio installs a number of shortcuts to command windows with the correct paths set for various purposes. These are written to the start menu folders for "Visual Studio 2013\Visual Studio Tools" and for "Microsoft Visual Studio 2012\Visual Studio Tools".
To find the version(s) installed you may be better looking in the directories where the Visual Studio software is installed. Places such as C:\Program Files and similar.