Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fix(cmake): Use right dir for xml proto files#12

Merged
patrick96 merged 1 commit into
polybar:masterfrom
patrick96:xcbincludedir
Oct 16, 2018
Merged

fix(cmake): Use right dir for xml proto files#12
patrick96 merged 1 commit into
polybar:masterfrom
patrick96:xcbincludedir

Conversation

@patrick96

@patrick96 patrick96 commented Feb 25, 2018

Copy link
Copy Markdown
Member

As described in polybar/polybar#750 ${XCBPROTO_PREFIX}/share/xcb may not
point to the directory containing the xml proto files

If cmake 3.4 or up is used, the proper path (stored in the xcbincludedir
variable in xcb-proto.pc) can be fetched. Older versions fall back to
the way it was done before

As described in polybar/polybar#750 ${XCBPROTO_PREFIX}/share/xcb may not
point to the directory containing the xml proto files

If cmake 3.4 or up is used, the proper path (stored in the xcbincludedir
variable in xcb-proto.pc) can be fetched. Older versions fall back to
the way it was done before
@jaagr

jaagr commented Mar 12, 2018

Copy link
Copy Markdown
Member

Is there anything left to be done here? The reason I ask is because the pull-request is still tagged with [WIP].

@patrick96

Copy link
Copy Markdown
Member Author

I'm still waiting on confirmation from @fedelodo that this actually works.

@patrick96 patrick96 changed the title [WIP] fix(cmake): Use right dir for xml proto files fix(cmake): Use right dir for xml proto files Oct 14, 2018
@patrick96

Copy link
Copy Markdown
Member Author

We just got confirmation that this works on Exherbo. So I think it's ready to be merged.

@patrick96 patrick96 requested a review from NBonaparte October 14, 2018 21:19

@NBonaparte NBonaparte left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine, if it works on exherbo then I guess it works.

@patrick96 patrick96 merged commit bf6ff36 into polybar:master Oct 16, 2018
@patrick96 patrick96 deleted the xcbincludedir branch October 16, 2018 16:17
patrick96 added a commit to polybar/polybar that referenced this pull request Dec 23, 2018
### Breaking Changes:
None

### Changelog

**New Config Options**
The following config options were added

In the `[settings]` section:
* `pseudo-transparency`

In `internal/cpu`:
* `ramp-coreload-spacing`, spacing between elements in `<ramp-coreload>` elements
* `%percentage-sum%` in `label`. Shows sum of all percentages

In `custom/script`:
* `double-click-left`
* `double-click-middle`
* `double-click-right`

In `internal/pulseaudio`:
* `interval`, volume increase and decrease steps in percentage points

In `internal/memory`:
* `bar-swap-used`
* `bar-swap-free`
* `ramp-swap-used`
* `ramp-swap-free`

**Deprecations**
* `tray-transparent` in the bar section is no longer used. The tray now always uses pseudo-transparency

**Features**
* volume: adjustable volume steps (#1364), see #1361
* memory: Add progress bars and ramps for swap (#1325)
* render: pseudo-transparency (always used in the tray)  (#595)
* cpu: 
    * Configurable spacing in between coreloads (#1472), see #1389
    * Non-normalized cpu load (#1517), see #1516
* script: Double click actions (#1442)
* net: Support for bridge interfaces (#1528), see #1522
* token: zero pad tokens when min-width value starts with a `0` (#1341), see #1332

**Fixes**
* config: Use font patterns detected on system in sample config (#1350)
* net: Disconnected module when SSID is only an emoji (#1371), see #1367
* tray: Tray overlapping with bar (#1392), see #591
* build: Several build errors (#1395, #1454, #1470, polybar/xpp#12, #1493), see #1447, #1469, #750, #1492
* mpd: format-online-prefix not working (#1402), see #1399
* font: Crash for some font-patterns (#1451), see #1435
* script: 
    * Only `%counter%` or `%pid%` token usable, never both (#1456)
    * click actions with colons in them (#1457), see #984
* renderer: Bar locks up when xorg composite extension is disabled (#1430), see #1425
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants