Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
W
wine-cw
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
wine
wine-cw
Commits
a270615f
Commit
a270615f
authored
May 25, 2004
by
Jon Griffiths
Committed by
Alexandre Julliard
May 25, 2004
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Always use $(CC) for building the generated .spec.c file.
parent
7109423e
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
1 deletion
+6
-1
winegcc.c
tools/winegcc/winegcc.c
+6
-1
No files found.
tools/winegcc/winegcc.c
View file @
a270615f
...
...
@@ -345,6 +345,7 @@ static void build(struct options* opts)
const
char
*
output_name
,
*
spec_file
,
*
lang
;
const
char
*
winebuild
=
getenv
(
"WINEBUILD"
);
int
generate_app_loader
=
1
;
int
old_processor
;
int
j
;
/* NOTE: for the files array we'll use the following convention:
...
...
@@ -532,8 +533,12 @@ static void build(struct options* opts)
spawn
(
opts
->
prefix
,
spec_args
);
/* compile the .spec.c file into a .spec.o file */
old_processor
=
opts
->
processor
;
/* Always compile spec.c as c, even if linking with g++ */
opts
->
processor
=
proc_cc
;
spec_o_name
=
compile_to_object
(
opts
,
spec_c_name
,
0
);
opts
->
processor
=
old_processor
;
/* link everything together now */
link_args
=
strarray_alloc
();
strarray_addall
(
link_args
,
get_translator
(
opts
));
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment