Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
K
KWSys
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Container Registry
Model registry
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Sylvain Joubert
KWSys
Commits
ef49afc7
Commit
ef49afc7
authored
18 years ago
by
Brad King
Browse files
Options
Downloads
Patches
Plain Diff
BUG: Use angle-brackets to include testSystemTools.h to avoid problems with in-source builds.
parent
4022db6d
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
testDynamicLoader.cxx
+3
-1
3 additions, 1 deletion
testDynamicLoader.cxx
testSystemTools.cxx
+3
-1
3 additions, 1 deletion
testSystemTools.cxx
with
6 additions
and
2 deletions
testDynamicLoader.cxx
+
3
−
1
View file @
ef49afc7
...
...
@@ -29,7 +29,9 @@
# include "kwsys_stl_string.hxx.in"
#endif
#include
"testSystemTools.h"
// Include with <> instead of "" to avoid getting any in-source copy
// left on disk.
#include
<testSystemTools.h>
kwsys_stl
::
string
GetLibName
(
const
char
*
lname
)
{
...
...
This diff is collapsed.
Click to expand it.
testSystemTools.cxx
+
3
−
1
View file @
ef49afc7
...
...
@@ -27,7 +27,9 @@
# include "kwsys_ios_iostream.h.in"
#endif
#include
"testSystemTools.h"
// Include with <> instead of "" to avoid getting any in-source copy
// left on disk.
#include
<testSystemTools.h>
#include
<string.h>
/* strcmp */
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment