ui_local.h: No such file or directory #1

LoudHoward opened this Issue Jan 30, 2012 · 3 comments


None yet

3 participants



can you submit this file?


Sure. Just do a pull request and I will review it. Have you filled out the contributers agreement?


Sent from my BlackBerry Wireless Handheld

----- Original Message -----
From: LoudHoward [mailto:reply@reply.github.com]
Sent: Monday, January 30, 2012 05:05 AM
To: Sean Paul Taylor
Subject: [Quake3] ui_local.h: No such file or directory (#1)


can you submit this file?

Reply to this email directly or view it on GitHub:

This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.



got the error if I compile the project:

Description Resource Path Location Type
ui_local.h: No such file or directory ui_vkb.c /quake3/code/q3_ui line 1 C/C++ Problem

ablake commented Jan 30, 2012

I see the problem, it's actually with the build config. Fixing now. I had edited the command line manually and left some include paths absolute rather than relative. Meanwhile I've found the options I was looking for under C/C++ Build -> Settings -> QCC Compiler -> Output Control, namely to disable "-fstack-protector-all" and to enable "-fPIE" for release mode, which means the command line can go back to using the configuration settings. I'll take a minute to test this and should then be able to check in the changes.

@ablake ablake added a commit that closed this issue Jan 30, 2012
@ablake ablake Fixes #1 60ab46b
@ablake ablake closed this in 60ab46b Jan 30, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment