Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
W
wine-winehq
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-winehq
Commits
de53c487
Commit
de53c487
authored
Apr 09, 2001
by
Andreas Mohr
Committed by
Alexandre Julliard
Apr 09, 2001
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Added uninstall hints.
parent
f552359c
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
12 additions
and
0 deletions
+12
-0
README
README
+4
-0
wineinstall
tools/wineinstall
+8
-0
No files found.
README
View file @
de53c487
...
...
@@ -124,6 +124,10 @@ Once Wine has been built correctly, you can do "make install"; this
will install the wine executable, the Wine man page, and a few other
needed files.
Don't forget to uninstall any conflicting previous Wine installation
first. Try either "dpkg -r wine" or "rpm -e wine" or "make uninstall"
before installing.
If you want to build the documentation, you can run "make" in the
documentation directory.
...
...
tools/wineinstall
View file @
de53c487
...
...
@@ -183,6 +183,14 @@ if [ $RET -eq 0 ]; then
fi
fi
# check whether wine binary still available
if
[
-n
"
`
which wine
`
"
]
;
then
echo
"Warning !! wine binary (still) found, which may indicate"
echo
"a (conflicting) previous installation."
echo
"You might want to abort and uninstall Wine first."
std_sleep
fi
# run the configure script, if necessary
if
[
-f
config.cache
]
&&
[
-f
Makefile
]
&&
[
Makefile
-nt
configure
]
...
...
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