Explore Enterprise Education Gitee Premium Gitee AI AI teammates
Fetch the repository succeeded.
Donate
Please sign in before you donate.
Scan WeChat QR to Pay
Cancel
Complete
Prompt
Switch to Alipay.
OK
Cancel
1 Star 0 Fork 20

peitingwei/IvorySQL

forked from IvorySQL/IvorySQL
Create your Gitee Account
Explore and code with more than 14 million developers,Free private repositories !:)
Sign up
Already have an account? Sign in
master
Branches (37)
Tags (552)
master
IVORY_REL_2_STABLE
IVORY_REL_1_STABLE
REL_15_STABLE
REL_13_STABLE
REL_14_STABLE
REL9_6_STABLE
REL_10_STABLE
REL_11_STABLE
REL_12_STABLE
REL9_5_STABLE
REL9_4_STABLE
REL9_3_STABLE
REL9_2_STABLE
REL9_1_STABLE
REL9_0_STABLE
REL8_2_STABLE
REL8_3_STABLE
REL8_4_STABLE
REL8_1_STABLE
Ivory_REL_2_1
Ivory_REL_1_5
Ivory_REL_1_4
Ivory_REL_1_3
Ivory_REL_1_2
Ivory_REL_1_1
Ivory_REL_1_0
REL_14_0
REL_14_RC1
REL9_6_23
REL_10_18
REL_11_13
REL_12_8
REL_13_4
REL_14_BETA3
REL_14_BETA2
REL_14_BETA1
REL9_6_22
REL_10_17
REL_11_12
master
Branches (37)
Tags (552)
master
IVORY_REL_2_STABLE
IVORY_REL_1_STABLE
REL_15_STABLE
REL_13_STABLE
REL_14_STABLE
REL9_6_STABLE
REL_10_STABLE
REL_11_STABLE
REL_12_STABLE
REL9_5_STABLE
REL9_4_STABLE
REL9_3_STABLE
REL9_2_STABLE
REL9_1_STABLE
REL9_0_STABLE
REL8_2_STABLE
REL8_3_STABLE
REL8_4_STABLE
REL8_1_STABLE
Ivory_REL_2_1
Ivory_REL_1_5
Ivory_REL_1_4
Ivory_REL_1_3
Ivory_REL_1_2
Ivory_REL_1_1
Ivory_REL_1_0
REL_14_0
REL_14_RC1
REL9_6_23
REL_10_18
REL_11_13
REL_12_8
REL_13_4
REL_14_BETA3
REL_14_BETA2
REL_14_BETA1
REL9_6_22
REL_10_17
REL_11_12
Clone or Download
Clone/Download
Prompt
To download the code, please copy the following command and execute it in the terminal
To ensure that your submitted code identity is correctly recognized by Gitee, please execute the following command.
When using the SSH protocol for the first time to clone or push code, follow the prompts below to complete the SSH configuration.
1 Generate RSA keys.
2 Obtain the content of the RSA public key and configure it in SSH Public Keys
To use SVN on Gitee, please visit the usage guide
When using the HTTPS protocol, the command line will prompt for account and password verification as follows. For security reasons, Gitee recommends configure and use personal access tokens instead of login passwords for cloning, pushing, and other operations.
Username for 'https://gitee.com': userName
Password for 'https://userName@gitee.com': # Private Token
master
Branches (37)
Tags (552)
master
IVORY_REL_2_STABLE
IVORY_REL_1_STABLE
REL_15_STABLE
REL_13_STABLE
REL_14_STABLE
REL9_6_STABLE
REL_10_STABLE
REL_11_STABLE
REL_12_STABLE
REL9_5_STABLE
REL9_4_STABLE
REL9_3_STABLE
REL9_2_STABLE
REL9_1_STABLE
REL9_0_STABLE
REL8_2_STABLE
REL8_3_STABLE
REL8_4_STABLE
REL8_1_STABLE
Ivory_REL_2_1
Ivory_REL_1_5
Ivory_REL_1_4
Ivory_REL_1_3
Ivory_REL_1_2
Ivory_REL_1_1
Ivory_REL_1_0
REL_14_0
REL_14_RC1
REL9_6_23
REL_10_18
REL_11_13
REL_12_8
REL_13_4
REL_14_BETA3
REL_14_BETA2
REL_14_BETA1
REL9_6_22
REL_10_17
REL_11_12
IvorySQL
/
src
/
tools
/
pginclude
contribute
Sync branch
See difference Through Pull Request Sync
Sync branch
Through Pull Request Sync
A Pull Request will be created to the current
branch and will be merged in to complete the sync
File empty ...
Notice: Creating folder will generate an empty file .keep, because not support in Git
Loading...
README
src/tools/pginclude/README
pginclude
=========
These utilities help clean up #include file usage. They should be run
in this order so that the include files have the proper includes before
the C files are tested.
pgfixinclude	change #include's to <> or ""
pgcompinclude [-v]
		report which #include files can not compile on their own
pgrminclude [-v]
		remove extra #include's
pgcheckdefines
		check for #ifdef tests on symbols defined in files that
		weren't included --- this is a necessary sanity check on
		pgrminclude
pgdefine	create macro calls for all defines in the file (used by
		the above routines)
It is also a good idea to sort the pg-specific include files in
alphabetic order. This is best done with a text editor. Typical usage
order would be:
	pgfixinclude
	sort include references
	run multiple times:
		pgcompinclude
		pgrminclude /src/include
	pgrminclude /
	pgcheckdefines
There is a complexity when modifying /src/include. If include file 1
includes file 2, and file 2 includes file 3, then when file 1 is
processed, it needs only file 2, not file 3. However, if later, include
file 2 is processed, and file 3 is not needed by file 2 and is removed,
file 1 might then need to include file 3. For this reason, the
pgcompinclude and pgrminclude /src/include steps must be run several
times until all includes compile cleanly.
Also, tests should be done with configure settings of --enable-cassert
and EXEC_BACKEND on and off. It is also wise to test a WIN32 compile.
Another tools that does a similar task is at:
	http://code.google.com/p/include-what-you-use/
An include file visualizer script is available at:
	http://archives.postgresql.org/pgsql-hackers/2011-09/msg00311.php
headerscheck
============
This script can be run to verify that all Postgres include files meet
the project convention that they will compile "standalone", that is
with no prerequisite headers other than postgres.h (or postgres_fe.h
or c.h, as appropriate).
A small number of header files are exempted from this requirement,
and are skipped by the headerscheck script.
The easy way to run the script is to say "make -s headerscheck" in
the top-level build directory after completing a build. You should
have included "--with-perl --with-python" in your configure options,
else you're likely to get errors about related headers not being found.
A limitation of the current script is that it doesn't know which headers
are for frontend or backend, so it tests everything with postgres.h
as prerequisite, even if postgres_fe.h would be more appropriate. Also
note that the contents of macros are not checked; this is intentional.
cpluspluscheck
==============
This script can be run to verify that all Postgres include files meet
the project convention that they will compile as C++ code. Although
the project's coding language is C, some people write extensions in C++,
so it's helpful for include files to be C++-clean.
A small number of header files are exempted from this requirement,
and are skipped by the cpluspluscheck script.
The easy way to run the script is to say "make -s cpluspluscheck" in
the top-level build directory after completing a build. You should
have included "--with-perl --with-python" in your configure options,
else you're likely to get errors about related headers not being found.
If you are using a non-g++-compatible C++ compiler, you may need to
override the script's CXXFLAGS setting by setting a suitable environment
value.
A limitation of the current script is that it doesn't know which headers
are for frontend or backend, so it tests everything with postgres.h
as prerequisite, even if postgres_fe.h would be more appropriate. Also
note that the contents of macros are not checked; this is intentional.
Report
Report success
We will send you the feedback within 2 working days through the letter!
Please fill in the reason for the report carefully. Provide as detailed a description as possible.
Please select a report type
Cancel
Send
误判申诉

此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。

如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。

取消
提交

About

No description
No labels
README
Apache-2.0
Use Apache-2.0
Cancel

Releases

No release

Contributors

All

Activities

can not load any more
Edit
About
Homepage
马建仓 AI 助手
尝试更多
代码解读
代码找茬
代码优化
C
1
https://gitee.com/peitingwei/IvorySQL.git
git@gitee.com:peitingwei/IvorySQL.git
peitingwei
IvorySQL
IvorySQL
master
Going to Help Center

Search

Comment
Repository Report
Back to the top
Login prompt
This operation requires login to the code cloud account. Please log in before operating.
Go to login
No account. Register

AltStyle によって変換されたページ (->オリジナル) /