Has compiled Matrox Imaging Library using Visual Studio 2010. I have downloaded MIL and trying to compile a simple program in the installed directory called 'msimple.cpp', but getting the following error:
I'm compiling some open source code (originally written for Linux / gcc) which uses the following line to determine if a particular section is being compiled for an x86 processor:-
im trying to compile a project that uses Open SSL but i have a problem since compiler complains about this on some headers
The files are empty and only containing this line:
"../../crypto/md5/md5.h"
I understood that those headers redirect to the actual file in a different path from the include folder, must work in other compilers but VS2013 complains about it.
Im planing to work arround it like copying those files directly in the include folder or even take the time to redirect those includes to the actual file one by one but im guessing that there is a simpler way.
I have a non-MFC static library which I share between a number of different projects, some non-MFC and some MFC. Currently the static library uses a typedef of std::wstring and std::string for UNICODE and non-UNICODE builds.
After discovering it's possible to use CString in non-MFC applications, by including atlstr.h header, I decided I'd rather that than using stl strings and having to keep converting between the different types. However, I seem to be struggling with linker errors when linking the library with a MFC application.
Can I create a non-MFC static library using CString from atlstr.h and link it with a MFC application?
For each project in a VS solution it's possible to stipulate per-project folders that get searched in addition to the folders that you've set globally for Visual Studio.
Which folders take priority? Do the project's folders get searched first? Or do the global folder get searched first? Or is it possible to select one set as having priority over the other?
I want to know how to list the all the symbols in the shared library(dll or .so file). I dont want commands like nm or objdump or depends.exe . I want to get the list of functions available in shared library programmatically at runtime (after calling loadlibrary/dlopen and GetProcAddress/dlsym). Is there a way to get the complete signature of functions in a shared library?
I am debugging a library. I can step into the code however the watch window doesn't show the values of any variables. It will display a message in the value field:
Code: m_pParentCXX0017: Error: symbol "m_pParent" not found
Interestingly it does show values for local variables in that function but not member functions. Most of my data members are member function though that I want to debug. I am using VS2010.
I am trying to include library paths in VS 2012 through the new property pages.I downloaded and installed mpich2-64 bit libraries under "C:Program FilesMPICH2include" and set the include path in Microsoft.cpp.x64.user property file so the path now looks like
#include <iostream> double fact (int f); //declaration of factorial function double power(double x, int y); //declaration of power function double sin(int x); //declaration of sine function //double cos(int x); //declaration of cosine function //double tan(int x); //declaration of tangent function
I've been reading about libraries; How to make them, how to use them, the different types of libraries, etc..
When using a shared library, does the program require that library to be installed on the computer after the program has been compiled into an .exe?
Ie.. if somebody downloaded a "Helloworld.exe" that I had compiled on my computer using a shared library (that wasn't part of a standard operating system), would they also need that shared library on their computer for the program to run without errors?
and for Static Libraries, when I compile a program using a static library, does it include in the final binary only the functions of the library that are actually used, or does the compiler add in the entire library?
I'm taking an intro to c++ class and during an exercise I ran into multiple errors that are out of my knowledge to fix. The rest of the class is using Visual and that is all the instructor knows so i'm in my own figuring out Xcode. Basically I wrote the same program twice but one has a different struct and I get all sorts of errors with it. understand what the errors are and why they occurred.
The working program is this:
#include <iostream> #include <fstream> #include <iomanip> #include <cmath> using namespace std; struct point { public: double x1,y1; double x2,y2;
[code]....
This program does not compile and I get the following errors:
stl_iterator_base_types.h
1) Symantic Issue No type named 'value_type' in 'myPoint' 2) Symantic Issue No type named 'iterator_category in 'myPoint' 3) Symantic Issue No type named 'difference_type' in 'myPoint' 4) Symantic Issue No type named 'pointer' in 'myPoint' 5) Symantic Issue No type named 'reference' in 'myPoint'
have several linux header files included and when I compile my program I get the below errors..Am I NOT supposed to use some of these headers? Source is below as well.Looking through the headers mentioned in these errors, it's looking like stuff really is defined in multiple places...
Code:
codeblox@Lubuntu-pc:~/Programming/C/Network/MITM/src$ gcc -g -o mitm *.c In file included from mitm.h:12:0, from create_raw.c:1: /usr/include/netpacket/packet.h:22:8: error: redefinition of ‘struct sockaddr_ll’ In file included from /usr/include/linux/netdevice.h:30:0, from /usr/include/linux/if_arp.h:26, from mitm.h:10, from create_raw.c:1: }
I've a problem compiling my makefile. The additional files are enclosed.
the error I get: $make ./main gcc -ggdb main.c /tmp/ccPIxwjP.o: In function `main': /home/ilan/Embedded_linux/Lesson-2-Makefiles/lesson-2.1/main.c:6: undefined reference to `func1' /home/ilan/Embedded_linux/Lesson-2-Makefiles/lesson-2.1/main.c:7: undefined reference to `func2' collect2: error: ld returned 1 exit status make: *** [main.o] Error 1 $
Code: my make file: main : main.o file1.o file2.o gcc -ggdb main.o file1.o file2.o -o gdb-main main.o : main.c file1.h file2.h
I want to use two separate files in 1 program, but cannot get it to work. I don't know if it's my files or the compiling thats wrong. I have never used 2 files in my programs so far. Only used #include <stdio.h>.
Here are my files: extern_static.c Code: extern int i; int main(void) {
Code: /* Demonstrates using the gets() return value. */ #include <stdio.h> /* Declare a character array to hold input, and a pointer. */ char input[257], *ptr;
[Code]....
I just got this from the book that I am using and it is for testing for input of a blank line and readers are being warned in using this format (line 18):
Code: while ( (*ptr = gets(input)) != NULL)
What is the correct syntax if a gcc compiler is to be used?
I have a FTP server, client program and thus I can easily transfer files, however what I want is to modify the program such that server receives a c/c++ file, compiles the output, and sends a text file back to the client containing the output. The program should also take note that errors are also transferred.
The number of parameters to this function is variable It has all types of variables, function calls, etc.
The code has thousands of these lines
There is now a need for a special version of the compile that will remove a lot of the code, among others is the logging.
Can I somehow #define the "logthis" name into something that'll remove all actual calls to the code. including the actual parameters/expressions to the call.
I can't afford to add #ifdef/#endif around each of the calls because there are too many of them, and because that'll cause some undisired side effects in our code conformance tests.
Code: #define logthis __noop
comes close, that removes the call, but it still causes the compiler to evaluate and validate all the parameters to the logthis function, which doesn't work because in this case, removing the logging headers also removes other members of the class that get used as part of the parameters to logthis()
if I could define logthis into // resulting in all the rest of the line being comments, but that doesn't work.
Preferably I'd like something to be portable, but I'll take a solution that only works on visual studio as well.
I'm trying to compile a library for use with PoLabs Pokeys 56U USB device (PoKeys56U) on Linux Mint 17 64-bit.
I'm using the information from here - New cross-platform library for all PoKeys devices - MyPokeys
When I run
sudo make -f Makefile.noqmake install
I get the following errors;In file included from PoKeysLibCore.c:22:0:
PoKeysLib.h:38:28: error: conflicting types for "int64_t" typedef long long int64_t; ^ In file included from /usr/include/stdlib.h:314:0, from PoKeysLibCore.c:21:
I'm creating a small command line game in C. I have never done anything cross platforms, but this is small enough (so far) that it might not be too bad.
When I am done, I'm not sure how it will be distributed: Either I will just send people the C files and say "compile on your system with these options", or I will just have executables for various systems. Probably Windows 7/8, Ubuntu, CentOS, and whatever I can find to test on.
I right now I'm testing/developing on Windows 7 using MinGW. So my questions are: while I'm developing, how should I be compiling/testing it?