files structure reorganization

git-svn-id: http://svn.miranda-ng.org/main/trunk@492 1316c22d-e87f-b044-9b9b-93d7a3e3ba9c

4 files changed, 0 insertions, 143 deletions

diff --git a/plugins/MirOTR/gpgvs.docs/authors.txt b/plugins/MirOTR/gpgvs.docs/authors.txt
deleted file mode 100644
index 5eef49c084..0000000000
--- a/plugins/MirOTR/gpgvs.docs/authors.txt
+++ /dev/null
@@ -1,7 +0,0 @@
-gpgvs

-building gnupg related projects with Visual Studio

-

-Authors:

-          Francesco Picasso

-          mr.s0rr0w@gmail.com

-          www.s0rr0w.net
\ No newline at end of file
diff --git a/plugins/MirOTR/gpgvs.docs/gpgvs.aim.txt b/plugins/MirOTR/gpgvs.docs/gpgvs.aim.txt
deleted file mode 100644
index c7cbd9272d..0000000000
--- a/plugins/MirOTR/gpgvs.docs/gpgvs.aim.txt
+++ /dev/null
@@ -1,22 +0,0 @@
-~~~

-AIM

-~~~

-the aim of *.vs projects is to provide a well organized

-and not invasive way to build target open source projects

-using visual studio (vs.6 and vs.net)

-

-~~~~~~

-REASON

-~~~~~~

-In many situations I was obliged to use visual studio in

-writing projects, and writing windows software is best suited

-using this ide.

-When I had need to use these great open source projects in

-my applications, I had to use the binaries provided (if) for

-the win32 environment: but, I think, if it can run in win32,

-it could also be built using win32 compiler/linker.

-I know you have to pay for visual studio, but why don't give

-the opportunity to build using this tool too?

-Moreover I think that providing these projects could increment

-the number of coworker programmers.

-So I decided to provide these visual studio projects.
\ No newline at end of file
diff --git a/plugins/MirOTR/gpgvs.docs/gpgvs.architecture.txt b/plugins/MirOTR/gpgvs.docs/gpgvs.architecture.txt
deleted file mode 100644
index 4a2c2511f9..0000000000
--- a/plugins/MirOTR/gpgvs.docs/gpgvs.architecture.txt
+++ /dev/null
@@ -1,108 +0,0 @@
-~~~~~~~~~~~~

-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/plugins/MirOTR/gpgvs.docs/readme.txt b/plugins/MirOTR/gpgvs.docs/readme.txt
deleted file mode 100644
index fd10f94900..0000000000
--- a/plugins/MirOTR/gpgvs.docs/readme.txt
+++ /dev/null
@@ -1,6 +0,0 @@
-gpgvs

-building gnupg related projects with Visual Studio

-

-for documents check them on sourceforge project site

-

-http://sourceforge.net/projects/gpgvs/
\ No newline at end of file