Re: [HACKERS] [Proposal]: Extends VisualStudio to automatically precompile EmbeddedSQL
Le 02/05/2017 à 13:22, Michael Paquier a écrit : > On Tue, May 2, 2017 at 6:35 PM, zosrothko wrote: >> Hi >> >> I made an extension of VisualStudio that precompiles automaticaly C or >> C++ source with PostgreSQL Embedded SQL. The extension is made of the 3 >> files joined and I have no idea where they should be placed in the >> PostgreSQL source tree. >> >> Anybody interested in pushing this extension? > The PostgreSQL uses a set of scripts in src/tools/msvc/ to generate > things compiled with visual studio, so instinctively you would be > looking at working on that. Honestly, just by looking at the files you > are proposing, it is hard to make an idea of why this would be useful > for ECPG, and please note as well that there are guidelines for > submitting patches: > https://wiki.postgresql.org/wiki/Submitting_a_Patch > > The source code of ecpg is located in src/interfaces/ecpg by the way. > If you are interested to work on it, that's the place where to look at > first. I need to add those three files in the installation process. Where should go those files? 1. in C:\Program Files (x86)\PostgreSQL\9.5\bin 2. or should I put those files in a share/contrib directory? Where is located the configuration file to change for putting those files in the Windows distribution? FA
[HACKERS] [Proposal]: Extends VisualStudio to automatically precompile EmbeddedSQL
Hi I made an extension of VisualStudio that precompiles automaticaly C or C++ source with PostgreSQL Embedded SQL. The extension is made of the 3 files joined and I have no idea where they should be placed in the PostgreSQL source tree. Anybody interested in pushing this extension? FA ecpg.props Description: XML document http://schemas.microsoft.com/developer/msbuild/2003";> EcpgTarget $(MSBuildThisFileDirectory)$(MSBuildThisFileName).xml @(Ecpg, '|') $(ComputeLinkInputsTargets); ComputeEcpgOutput; $(ComputeLibInputsTargets); ComputeEcpgOutput;  http://schemas.microsoft.com/winfx/2006/xaml"; xmlns:sys="clr-namespace:System;assembly=mscorlib" xmlns:transformCallback="Microsoft.Cpp.Dev10.ConvertPropertyCallback"> General Ecpg Options Command Line https://www.postgresql.org/docs/9.5/static/app-ecpg.html"; DisplayName="Output File Name" Description="Specifies that ecpg should write all its output to the given filename" Switch="o [value]" /> https://www.postgresql.org/docs/9.5/static/app-ecpg.html"; Description="Define a C preprocessor symbol." Switch="D [value]" /> https://www.postgresql.org/docs/9.5/static/app-ecpg.html"; Description="Specify an additional include path, used to find files included via EXEC SQL INCLUDE. Defaults are . (current directory), /usr/local/include, the PostgreSQL include directory which is defined at compile time (default: /usr/local/pgsql/include), and /usr/include, in that order." Switch="D [value]" /> https://www.gnu.org/software/ecpg/manual/html_node/Understanding.html#Understanding"; Switch="v" /> https://www.postgresql.org/docs/9.5/static/app-ecpg.html"; Switch="t" /> https://www.postgresql.org/docs/9.5/static/app-ecpg.html"; Switch="c" /> https://www.postgresql.org/docs/9.5/static/app-ecpg.html"; Switch="i" /> https://www.postgresql.org/docs/9.5/static/app-ecpg.html"; DisplayName="RunTime" Description="Selects run-time behavior. Option can be one of the following: no_indicator: Do not use indicators but instead use special values to represent null values. Historically there have been databases using this approach. prepare: Prepare all statements before using them. Libecpg will keep a cache of prepared statements and reuse a statement if it gets executed again. If the cache runs full, libecpg will free the least used statement. questionmarks: Allow question mark as placeholder for compatibility reasons. This used to be the default long ago."> https://www.postgresql.org/docs/9.5/static/app-ecpg.html"; DisplayName="CompatibilityMode" Description="Set a compatibility mode. mode can be INFORMIX or INFORMIX_SE."> Execute Before Specifies the targets for the build customization to run before. Execute After Specifies the targets for the build customization to run after. Additional Options Additional Options -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
