You shouldn't try to install untill it builds properly - just use `make`.
As far as the errors, you'd need to say what they are.
]]>Now, for your question: the + and - signs are part of the diff-file format. The pluses are lines that should be added to dwm.c, the minus are lines already in the original that should be removed. Lines without pluses or minuses are just context lines to figure out where this is supposed to go; do not add the context lines to dwm.c, they're already there.
Also, a patch has lines that (I think) begin with an @. These are also just instructions on which file to patch and an estimate of which line number to start at.
Lastly, when done, yes, save it as dwm.c. You are just editing the original dwm.c, right?
]]>No, you're not doing anything wrong. Let me explain:
Patches made by people are usually patched against a clean, vanilla dwm.c. This means that when you want to apply multiple patches, you will have to adapt those that will be patched against a non-vanilla dwm.c. To do so you can first apply patch A, then hand-patch patch B and create a new .diff file which will be patch B, made to be patched against a dwm.c which was patched with patch A. Savvy?
That's why you see my patches are numbered. It's a queue. The systray patch is the fourth, which means it was patched against XFT, pertag2 and uselessgaps. Because you don't use those, it can't find the code it should edit. That's why it's failing. To fix this, first patch a vanilla dwm.c with XFT and then hand-patch the systray in:
1. Patch vanilla dwm.c with XFT;
2. Open the systray patch in an editor and also open the just patched dwm.c;
3. Search for the lines to replace that are listed in the systray patch and apply these changes to the patched dwm.c;
4. When done, create a new .diff file of the systray patch that's patched against the XFT patched dwm.c:diff -u <hand-patched dwm.c> <xft-patched dwm.c> >> 02-dwm-6.0-systray.diff
Hi again I decide to try again with patching dwm. So far:
1. Done
2. Done
3. Ok i find the lines and applied them to xft patched dwm.c, but should i remove the "+" and "-" sings or i just leave them? And when i'm done.. i just save xft patched dwm.c or...?
Sorry for bad english and thanks again
]]>Start your own thread rather than bumping someone elses.
You quote me in suggesting a solution to someone else's problem - but that is not relevant to your issue.
We have no idea what you have done to get where you are now. I can see what you have not done: you have not read this thread and applied the patches as described.
]]>you have to add -I/usr/include/freetype2 to your CFLAGS and -lfreetype to your LDFLAGS
Hi, this is what i get
==> Making package: dwm 6.0-1 (Wed May 15 13:37:05 EEST 2013)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing src/ tree
==> Removing existing pkg/ directory...
==> Starting build()...
dwm build options:
CFLAGS = -I/usr/include/freetype2 -std=c99 -pedantic -Wall -Os -I. -I/usr/include -I/usr/include/X11 -D_FORTIFY_SOURCE=2 -DVERSION="6.0" -DXINERAMA
LDFLAGS = -lfreetype -s -L/usr/lib -lc -L/usr/lib/X11 -lX11 -L/usr/lib/X11 -lXinerama
CC = cc
CC dwm.c
dwm.c: In function ‘keypress’:
dwm.c:1062:2: warning: ‘XKeycodeToKeysym’ is deprecated (declared at /usr/include/X11/Xlib.h:1695) [-Wdeprecated-declarations]
keysym = XKeycodeToKeysym(dpy, (KeyCode)ev->keycode, 0);
^
CC -o dwm
dwm.o: In function `getcolor':
dwm.c:(.text+0x994): undefined reference to `XftColorAllocName'
dwm.o: In function `textnw':
dwm.c:(.text+0xabe): undefined reference to `XftTextExtentsUtf8'
dwm.o: In function `drawtext':
dwm.c:(.text+0xcdc): undefined reference to `XftDrawCreate'
dwm.c:(.text+0xd33): undefined reference to `XftDrawStringUtf8'
dwm.c:(.text+0xd3b): undefined reference to `XftDrawDestroy'
dwm.o: In function `main':
dwm.c:(.text.startup+0x115): undefined reference to `XftFontOpenName'
dwm.c:(.text.startup+0x138): undefined reference to `XftFontOpenName'
collect2: error: ld returned 1 exit status
make: *** [dwm] Error 1
==> ERROR: A failure occurred in build().
Aborting...
suggestions?
]]>