Fail to run tests in VS2012
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 28/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cmake
- Domain
- build-system, testing
Research direction
Reproduce the failure by building OpenCurrent with CMake, opening the RUN_TESTS project in Visual Studio 2012, and building the solution on the stated Windows 7, CUDA 5.5 setup. Start by capturing the unresolved external symbol diagnostics; done means the generated RUN_TESTS project builds successfully.
Written by the indexing model from the issue text.
Description
What steps will reproduce the problem?
1. Build OpenCurrent with CMake
2. Open RUN_TESTS project in VS2012
3. Build solution
4. Build failure due to unresolved external symbols
What version of the product are you using? On what operating system?
OpenCurrent 1.1.0
Windows 7 64-bits
Visual Studio 2012
CUDA 5.5
Please provide any additional information below.
I have also tried to create a new empty project, add OpenCurrent files into it,
fix includes then build the project but still some unresolved external symbols
errors are thrown.
Original issue reported on code.google.com by fredvi...@gmail.com on 4 Sep 2013 at 2:15
- Dominant language
- Cuda
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ExpectationMax/opencurrent
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
ExpectationMax/opencurrent#23 · 1 comment ·
-
all tests failed Openauto-migrated Priority-Medium Type-Defect
Difficulty 4/5 3-5 days Newbie friendliness 25/100
ExpectationMax/opencurrent#20 · 1 comment ·
-
auto-migrated Priority-Medium Type-Defect
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
auto-migrated Priority-Medium Type-Defect
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
ExpectationMax/opencurrent#17 · 1 comment ·
-
auto-migrated Priority-Medium Type-Defect
Difficulty 3/5 1-2 days Newbie friendliness 25/100
ExpectationMax/opencurrent#18 · 1 comment ·
All issues in ExpectationMax/opencurrent
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
area:engineering priority:p2 type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jejjohnson/pyrox#234 ·
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
ros2/ros2_tracing#266 · 1 comment ·