1 files changed, 108 insertions, 0 deletions
diff --git a/linden/indra/gpg.vs/docs/gpgvs.architecture.txt b/linden/indra/gpg.vs/docs/gpgvs.architecture.txt
new file mode 100755
index 0000000..4a2c251
--- /dev/null
+++ b/linden/indra/gpg.vs/docs/gpgvs.architecture.txt
@@ -0,0 +1,108 @@
+~~~~~~~~~~~~
+ARCHITECTURE
+~~~~~~~~~~~~
+I admit that architecture meaning is too much for this project,
+but with this document I explain how is built and
+how to use these projects.
+First of all you should respect the directory structure otherwise
+projects will not compile, but obviously you can change it:
+rembember to change vs workspace relativ paths too.
+Regarding workspaces compile flags: I decided to not provide particular
+building flags, so if you have to optimize (or anything else) you
+have to change settings.
+~~~~~~~~~~~
+DIRECTORIES
+~~~~~~~~~~~
+As said in “aim” document, I do not want to get inside original
+source code, less than it is not forced:
+so the first step is to look at directories structure (not whole)
+[anywhwere]\
+           \libgcrypt-1.2.1\
+           \libgcrypt-1.2.1\
+           \[...]
+           \gpg.vs\bin.vs\
+                  \inc.vs\
+                  \libgcrypt-1.2.1.vs\
+                  \libgpg-error-1.1.vs\custom\
+                                      \libgpg_error_1_1.dsp
+                                      \libgpg_error_1_1.dsw
+There is a "root" directory, use whatever you want:
+inside this directory extract the original package, like
+libgcrypt-1.2.1, libgcrypt-1.2.1 and so on.
+Inside the "root" download/extract gpg.vs (otr.vs) project:
+you should have at least the same directories structure just shown.
+Inside you have "[original.package.name].vs" and all tools to be
+able to build original packages with visual studio.
+~~~~~~
+bin.vs
+~~~~~~
+here we'll go binaries created by visual studio, as
+\bin.vs\libgpg-error-1.1\debug\static\...
+\bin.vs\libgpg-error-1.1\release\static\...
+\bin.vs\libgpg-error-1.1\release\dll\...
+~~~~~~
+inc.vs
+~~~~~~
+this folder contains include files needed to build original packages
+without changing their code, like empty "socket.h" headers;
+and you will find "hooked" includes (like stddef.h) useful to declare
+definition that visual studio misses (like pid_t)
+~~~~~~~~~~~~~~~~~
+package.vs.custom
+~~~~~~~~~~~~~~~~~
+here you'll always find package->"config.h" header, made "by hand".
+You will find some others files that under *nix are automatically
+created, and I provide them in a "custom" way
+~~~~~~~
+EXAMPLE
+~~~~~~~
+You want to compile with vs libgpg-error-1.1.: choose your parent directory,
+in my case “gnu”
+\gnu\
+download and extract here the libgpg-error-1.1, so now I have
+\gnu\libgpg-error-1.1\libgpg-error\[source code]
+basically extract always in libgpg-error directory and the
+closest parent is libgpg-error-version, to have
+\gnu\libgpg-error-1.0\libgpg-error\[source code]
+\gnu\libgpg-error-1.1\libgpg-error\[source code]
+Now download gpg.vs project (or take it from cvs), which includes
+vs project for libgpg-error, and extract it in the directory
+you have choosen (gnu in my case),
+\gnu\gpg.vs\
+In gpg.vs directory find the libgpg-error-1.1.vs
+(appending .vs at the end of package name is the “standard” for this project)
+\gnu\gpg.vs\ libgpg-error-1.1.vs\
+And inside find the dsw/dsp of the project
+libgpg_error_1_1.dsw
+libgpg_error_1_1.dsp
+Note: the little change to names is due to vs limitations.
+You  have only to build it.
+The binaries files will be created in 
+\gnu\gpg.vs\bin.vs\libgpg-error.1.1\debug
+\gnu\gpg.vs\bin.vs\libgpg-error.1.1\release
+\ No newline at end of file

diff --git a/linden/indra/gpg.vs/docs/gpgvs.architecture.txt b/linden/indra/gpg.vs/docs/gpgvs.architecture.txt new file mode 100755 index 0000000..4a2c251 --- /dev/null +++ b/linden/indra/gpg.vs/docs/gpgvs.architecture.txt
@@ -0,0 +1,108 @@
	1	~~~~~~~~~~~~
	2	ARCHITECTURE
	3	~~~~~~~~~~~~
	4	I admit that architecture meaning is too much for this project,
	5	but with this document I explain how is built and
	6	how to use these projects.
	7	First of all you should respect the directory structure otherwise
	8	projects will not compile, but obviously you can change it:
	9	rembember to change vs workspace relativ paths too.
	10	Regarding workspaces compile flags: I decided to not provide particular
	11	building flags, so if you have to optimize (or anything else) you
	12	have to change settings.
	13
	14
	15	~~~~~~~~~~~
	16	DIRECTORIES
	17	~~~~~~~~~~~
	18	As said in “aim” document, I do not want to get inside original
	19	source code, less than it is not forced:
	20	so the first step is to look at directories structure (not whole)
	21
	22
	23	[anywhwere]\
	24	\libgcrypt-1.2.1\
	25	\libgcrypt-1.2.1\
	26	\[...]
	27	\gpg.vs\bin.vs\
	28	\inc.vs\
	29	\libgcrypt-1.2.1.vs\
	30	\libgpg-error-1.1.vs\custom\
	31	\libgpg_error_1_1.dsp
	32	\libgpg_error_1_1.dsw
	33
	34	There is a "root" directory, use whatever you want:
	35	inside this directory extract the original package, like
	36	libgcrypt-1.2.1, libgcrypt-1.2.1 and so on.
	37	Inside the "root" download/extract gpg.vs (otr.vs) project:
	38	you should have at least the same directories structure just shown.
	39	Inside you have "[original.package.name].vs" and all tools to be
	40	able to build original packages with visual studio.
	41
	42
	43	~~~~~~
	44	bin.vs
	45	~~~~~~
	46	here we'll go binaries created by visual studio, as
	47	\bin.vs\libgpg-error-1.1\debug\static\...
	48	\bin.vs\libgpg-error-1.1\release\static\...
	49	\bin.vs\libgpg-error-1.1\release\dll\...
	50
	51
	52	~~~~~~
	53	inc.vs
	54	~~~~~~
	55	this folder contains include files needed to build original packages
	56	without changing their code, like empty "socket.h" headers;
	57	and you will find "hooked" includes (like stddef.h) useful to declare
	58	definition that visual studio misses (like pid_t)
	59
	60
	61	~~~~~~~~~~~~~~~~~
	62	package.vs.custom
	63	~~~~~~~~~~~~~~~~~
	64	here you'll always find package->"config.h" header, made "by hand".
	65	You will find some others files that under *nix are automatically
	66	created, and I provide them in a "custom" way
	67
	68
	69	~~~~~~~
	70	EXAMPLE
	71	~~~~~~~
	72	You want to compile with vs libgpg-error-1.1.: choose your parent directory,
	73	in my case “gnu”
	74
	75	\gnu\
	76
	77	download and extract here the libgpg-error-1.1, so now I have
	78
	79	\gnu\libgpg-error-1.1\libgpg-error\[source code]
	80
	81	basically extract always in libgpg-error directory and the
	82	closest parent is libgpg-error-version, to have
	83
	84	\gnu\libgpg-error-1.0\libgpg-error\[source code]
	85	\gnu\libgpg-error-1.1\libgpg-error\[source code]
	86
	87	Now download gpg.vs project (or take it from cvs), which includes
	88	vs project for libgpg-error, and extract it in the directory
	89	you have choosen (gnu in my case),
	90
	91	\gnu\gpg.vs\
	92
	93	In gpg.vs directory find the libgpg-error-1.1.vs
	94	(appending .vs at the end of package name is the “standard” for this project)
	95
	96	\gnu\gpg.vs\ libgpg-error-1.1.vs\
	97
	98	And inside find the dsw/dsp of the project
	99
	100	libgpg_error_1_1.dsw
	101	libgpg_error_1_1.dsp
	102
	103	Note: the little change to names is due to vs limitations.
	104	You have only to build it.
	105	The binaries files will be created in
	106
	107	\gnu\gpg.vs\bin.vs\libgpg-error.1.1\debug
	108	\gnu\gpg.vs\bin.vs\libgpg-error.1.1\release \ No newline at end of file