CN116301897A - Method and system for verifying demo and link library through vs2008 one-key - Google Patents
Method and system for verifying demo and link library through vs2008 one-key Download PDFInfo
- Publication number
- CN116301897A CN116301897A CN202310275551.8A CN202310275551A CN116301897A CN 116301897 A CN116301897 A CN 116301897A CN 202310275551 A CN202310275551 A CN 202310275551A CN 116301897 A CN116301897 A CN 116301897A
- Authority
- CN
- China
- Prior art keywords
- lib
- dll
- demo
- solution
- library
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 20
- 230000001419 dependent effect Effects 0.000 claims abstract description 16
- 238000012795 verification Methods 0.000 claims description 21
- 230000003068 static effect Effects 0.000 claims description 5
- 238000011161 development Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Human Computer Interaction (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a method for verifying a demo and a link library through a vs2008 one-key, wherein the link library comprises a DLL and a LIB, and the method comprises the following steps: opening a solution of the link library project by using vs2008, and dragging the generated demo project into the solution of the link library project; entering a solution property page, selecting a single starting item, designating the single starting item as a corresponding demo item name, and setting a dependent item as a corresponding link library item name; entering a link library engineering attribute page, generating a compiled link library into a lib folder, and outputting all header files into an include folder; entering an attribute page of the demo project, adding a catalog, introducing a LIB library corresponding to the LIB, modifying the LIB, directly running the solution, if the LIB library corresponding to the DLL is introduced, setting a command line again, copying the DLL to an output catalog before generating an exe file, directly running the solution after modifying the DLL, and directly running the latest content of the link library after modifying the link library by one key.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and a system for verifying a demo and a link library through a vs2008 one-key.
Background
LIB is a static link Library, is an abbreviation of Library, codes in LIB are compiled into a target module (EXE or DLL) during static building, and after compiling is completed, the content of the LIB is already in the target module; DLLs are dynamically linked libraries, an abbreviation for Dynamic Link Library, a library of code and data that can be used by multiple programs simultaneously. In windows development, DLLs and libs are alternatives when writing a component, differing only from static and dynamic libraries. After a LIB is generated, it is usually necessary to verify whether its function is normal or meets the expected requirement, and at this time, a copy of the demo is written specifically for verifying the function of the LIB or DLL. The general flow is to generate LIB or DLL, manually copy the header file to the appointed path, copy LIB to the appointed directory, compile and run the demo, or compile demo, copy DLL to the corresponding EXE directory generated by demo, and then run the EXE file, which is time-consuming and labor-consuming and affects the development progress.
Disclosure of Invention
In order to overcome the above problems, the present invention is to provide a method and a system for verifying a demo and a link library by one key in vs2008, in which after modifying the LIB or DLL in the vs2008 environment, the demo can be directly run without performing a complicated copy operation manually.
The invention is realized by adopting the following scheme:
a method for one-touch verification of a demo and a link library by vs2008, wherein the link library comprises a dynamic link library DLL and a static link library LIB, and the method comprises the following steps:
step S1, using vs2008 to open the solution of the DLL or LIB project, and dragging the generated demo project into the solution of the DLL or LIB project;
s2, entering a solution attribute page, selecting a starting item under a general attribute, selecting a single starting item, and designating the single starting item as a corresponding demo item name;
s3, entering a solution attribute page, selecting an item dependent item under a general attribute, selecting a corresponding demo item name, and setting the dependent item as a corresponding DLL or LIB item name;
s4, entering an attribute page of DLL or LIB engineering, setting an output catalog, and generating a compiled DLL or LIB library into a LIB folder;
s5, entering an attribute page of DLL or LIB engineering, setting a command line, and outputting all header files to an include folder;
s6, entering an attribute page of the demo project, adding a directory in an additional library directory, introducing a LIB library corresponding to the LIB, directly running a solution after modifying the LIB, calling by the demo at the moment to be the latest LIB content, and continuing to enter the step S7 if the LIB library corresponding to the DLL is introduced;
and S7, entering an attribute page of the demo project, setting a command line again, copying the DLL to an output directory before generating the exe file, and directly running the solution after modifying the DLL, wherein the call of demo is the latest DLL content.
Further, step S1 is further specifically: the vs2008 is used to open the solution of the DLL or LIB project and to pull the generated demo project into the solution of the DLL or LIB project, which is the file of. sln, which is the file of.vcproj.
Further, step S4 is further specifically: entering an attribute page of DLL or LIB engineering, selecting a convention under configuration attributes, fixedly setting an output catalog to be./ LIB/LIB, and generating a compiled DLL or LIB library into a LIB folder.
Further, step S5 is further specifically: and entering an attribute page of the DLL or LIB engineering, selecting a generated event in the generated events under the configuration attribute, setting a command line as copy $ (solutionDir) \lib\include, and outputting all header files into an include folder.
Further, step S6 is further specifically: entering an attribute page of the demo project, selecting a routine in a linker under configuration attribute, adding $ (SolutionDir) LIB/LIB in an additional library catalog, introducing the LIB library corresponding to the LIB, and directly running a solution after modifying the LIB, wherein the latest LIB content is called by the demo.
Further, step S7 is further specifically: entering an attribute page of the demo project, selecting a pre-generated event in the generated events under the configuration attribute, setting a command line as copy $ (SolutionDir) lib\lib · DLL $ (OutDir), copying DLL to an output directory before generating exe, and directly running a solution after modifying the DLL, wherein the call of demo is the latest DLL content.
A system for verifying a demo and a link library by one key of vs2008, wherein the system comprises a scheme generating module, a starting item setting module, a dependent item setting module, an output catalog setting module, a header file output module, a LIB one-key verification module and a DLL one-key verification module;
the scheme generating module is used for opening the solution of the DLL or LIB engineering by using vs2008 and dragging the generated demo engineering into the solution of the DLL or LIB engineering;
the starting item setting module is used for entering a solution attribute page, selecting a starting item under a general attribute, selecting a single starting item and designating the single starting item as a corresponding demo item name;
the dependency item setting module is used for entering a solution attribute page, selecting an item dependency item under a general attribute, selecting a corresponding demo item name, and setting the dependency item as a corresponding DLL or LIB item name;
the output catalog setting module is used for entering attribute pages of DLL or LIB engineering, setting an output catalog, and generating a compiled DLL or LIB library into a LIB folder;
the header file output module is used for entering a property page of DLL or LIB engineering, setting a command line and outputting all header files to an include folder;
the LIB one-key verification module is used for entering an attribute page of the amo-removing project, adding a directory in an additional library directory, introducing a LIB library corresponding to the LIB, directly running a solution after modifying the LIB at the moment, calling by the amo at the moment to be the latest LIB content, and continuously entering the DLL one-key verification module if the LIB library corresponding to the DLL is introduced;
the DLL one-key verification module is used for entering an attribute page of the demo project, setting a command line again, copying the DLL to an output directory before generating an exe file, and directly running a solution after modifying the DLL at the moment, wherein the demo call is the latest DLL content.
Further, the scheme generating module further specifically includes: the vs2008 is used to open the solution of the DLL or LIB project and to pull the generated demo project into the solution of the DLL or LIB project, which is the file of. sln, which is the file of.vcproj.
Further, the output catalog setting module is further specifically: entering an attribute page of DLL or LIB engineering, selecting a convention under configuration attributes, fixedly setting an output catalog to be./ LIB/LIB, and generating a compiled DLL or LIB library into a LIB folder.
Further, the header file output module is further specifically: and entering an attribute page of the DLL or LIB engineering, selecting a generated event in the generated events under the configuration attribute, setting a command line as copy $ (solutionDir) \lib\include, and outputting all header files into an include folder.
Further, the LIB one-key verification module is further specifically: entering an attribute page of the demo project, selecting a routine in a linker under configuration attribute, adding $ (SolutionDir) LIB/LIB in an additional library catalog, introducing the LIB library corresponding to the LIB, and directly running a solution after modifying the LIB, wherein the latest LIB content is called by the demo.
Further, the DLL one-key verification module is further specifically: entering an attribute page of the demo project, selecting a pre-generated event in the generated events under the configuration attribute, setting a command line as copy $ (SolutionDir) lib\lib · DLL $ (OutDir), copying DLL to an output directory before generating exe, and directly running a solution after modifying the DLL, wherein the call of demo is the latest DLL content.
The invention has the beneficial effects that:
according to the method and the system for verifying the demo and the link library through the vs2008 one-key, through configuring the related attributes of the solution and the engineering and using the corresponding command line script, after the LIB or the DLL is modified through one key, the demo can directly run the processing scheme of the latest LIB or DLL content.
Drawings
FIG. 1 is a schematic flow chart of the method of the present invention;
FIG. 2 is a block diagram of the system of the present invention;
Detailed Description
The invention is further described below with reference to the accompanying drawings.
A method for verifying a demo and a link library by one key of vs2008, comprising the following steps:
step S1, using vs2008 to open the solution of the DLL or LIB project, and dragging the generated demo project into the solution of the DLL or LIB project;
s2, entering a solution attribute page, selecting a starting item under a general attribute, selecting a single starting item, and designating the single starting item as a corresponding demo item name;
s3, entering a solution attribute page, selecting an item dependent item under a general attribute, selecting a corresponding demo item name, and setting the dependent item as a corresponding DLL or LIB item name;
s4, entering an attribute page of DLL or LIB engineering, setting an output catalog, and generating a compiled DLL or LIB library into a LIB folder;
s5, entering an attribute page of DLL or LIB engineering, setting a command line, and outputting all header files to an include folder;
s6, entering an attribute page of the demo project, adding a directory in an additional library directory, introducing a LIB library corresponding to the LIB, directly running a solution after modifying the LIB, calling by the demo at the moment to be the latest LIB content, and continuing to enter the step S7 if the LIB library corresponding to the DLL is introduced;
s7, entering an attribute page of the demo project, setting a command line again, copying the DLL to an output directory before generating an exe file, and directly running a solution after modifying the DLL at the moment, wherein the call of demo is the latest DLL content;
the invention is further described with reference to the following specific examples:
a method for verifying a demo and a link library by one key of vs2008, comprising the following steps:
the first and verified file is LIB:
step S1, opening the solution of the LIB project using vs2008 (. Sln file), and dragging the created demo project (.vcproj file) into the solution of the LIB project (. Sln file).
The detailed steps for generating the solution are as follows:
1. creating a TestLIB project, and generating a solution;
2. opening the solution by VS 2008;
3. in the open solution, right click on the solution 'TestLIB' item, select add- > existing item, introduce the TestLIBdemo item into the solution.
S2, entering a solution attribute page, selecting a starting item under a general attribute, selecting a single starting item, and designating the single starting item as a corresponding demo item name;
wherein right-click the solution 'TestLIB' item, select an attribute;
in the displayed property page, the universal property is opened, the launch item is selected, the single launch item is selected, and set to TestLIBdemo.
And S3, entering a solution property page, selecting an item dependent item under a general property, selecting a corresponding demo item name, and setting the dependency as a corresponding LIB item name.
Wherein right-click the solution 'TestLIB' item, select an attribute;
in the displayed properties page, the generic properties are opened, item dependent items are selected, items are selected as TestLIBdemo, and in the lower dependent options TestLIB is checked.
And S4, entering an attribute page of the LIB project, selecting a convention under configuration attribute, fixedly setting an output catalog to be./ LIB/LIB, and generating a compiled LIB library into a LIB folder.
Wherein right clicking on the item 'TestLIB' item selects the attribute.
In the displayed properties page, the configuration properties are opened, the routine is selected, and the output catalog is set to./ lib/lib.
And S5, entering an attribute page of the LIB project, selecting a generated event in the generated events under the configuration attribute, setting a command line as copy $ (ProjectDir) ·h $ (solutionDir) \lib\include, and outputting all header files to an include folder.
Wherein right-click the solution 'TestLIB' item, select an attribute;
in the displayed attribute page, a configuration attribute is opened, a generation event is opened, a generated event under the generation event is selected, and a command line in the generated event is set as copy $ (ProjectDir) $ (solutionDir) \lib\include;
and setting a command behavior shell command, namely copying all the h files under the SolutionDir directory into a specified lib/include, wherein a plurality of commands can be set, and copying the specified header files.
And S6, entering an attribute page of the demo project, selecting a routine in a linker under configuration attribute, adding $ (SolutionDir) lib\lib in an additional library catalog, and introducing the LIB library corresponding to the LIB.
Wherein right clicking on the solution 'TestLIBdemo' item selects an attribute;
in the displayed attribute page, opening configuration attributes, opening a linker, selecting a convention under the linker, clicking a configuration button on the right side of the additional library catalog, adding $ (SolutionDir) lib\lib, and storing;
wherein, selecting the input under the linker, adding a testlib. Lib line in the additional dependency;
in step S7, after the LIB is modified, the solution can be directly operated, and the latest LIB content is called by the demo.
The second case, the validated file is a DLL:
step S1, using vs2008 to open the solution of the DLL project (. Sln file), and drag the generated demo project (.vcproj file) into the solution of the DLL project (. Sln file).
The detailed steps for generating the solution are as follows:
1. creating a TestDLL project, and generating a solution;
2. opening the solution by VS 2008;
3. in the open solution, right click on the solution 'TestDLL' item, select add- > existing item, introduce the TestDLLdemo item into the solution.
S2, entering a solution attribute page, selecting a starting item under a general attribute, selecting a single starting item, and designating the single starting item as a corresponding demo item name;
wherein right click on the solution 'TestDLL' item, select an attribute;
in the displayed attribute page, opening a general attribute, selecting a starting item, selecting a single starting item, and setting the single starting item as TestDLLdemo;
and S3, entering a solution property page, selecting an item dependent item under a general property, selecting a corresponding demo item name, and setting the dependency as a corresponding DLL item name.
Wherein right click on the solution 'TestDLL' item, select an attribute;
in the displayed property page, the generic property is opened, the item dependent item is selected, the item is selected as TestDLLdemo, and in the lower dependent options, the TestDLL is checked.
And S4, entering an attribute page of the DLL engineering, selecting a convention under configuration attribute, fixedly setting an output catalog to be./ lib/lib, and generating a compiled DLL library into a lib folder.
Wherein right clicking on the item 'TestDLL' item selects an attribute;
in the displayed properties page, the configuration properties are opened, the routine is selected, and the output catalog is set to./ lib/lib.
And S5, entering an attribute page of the DLL project, selecting a generated event in the generated events under the configuration attribute, setting a command line as copy $ (ProjectDir) $ (solutionDir) \lib\include, and outputting all header files to an include folder.
Wherein right click on the solution 'TestDLL' item, select an attribute;
in the displayed attribute page, a configuration attribute is opened, a generation event is opened, a generated event under the generation event is selected, and a command line in the generated event is set as copy $ (ProjectDir) $ (solutionDir) \lib\include;
and setting a command behavior shell command, namely copying all the h files under the SolutionDir directory into a specified lib/include, wherein a plurality of commands can be set, and copying the specified header files.
And S6, entering an attribute page of the demo project, selecting a routine in a linker under configuration attribute, adding $ (SolutionDir) lib\lib in an additional library catalog, and introducing a lib library corresponding to the DLL.
Wherein right click on the solution 'TestDLLdemo' item, select an attribute;
in the displayed attribute page, opening configuration attributes, opening a linker, selecting a convention under the linker, clicking a configuration button on the right side of the additional library catalog, adding $ (SolutionDir) lib\lib, and storing;
wherein the input under the linker is selected and the testdll. Lib line is added in the additional dependency.
Step S7, entering an attribute page of the demo project, selecting a pre-generated event in the generated events under the configuration attribute, setting a command line as copy $ (SolutionDir) lib\lib · dll $ (OutDir), and copying dll to an output directory before generating exe.
Wherein right click on the solution 'TestDLLdemo' item, select an attribute;
in the displayed attribute page, opening a configuration attribute, opening a generation event, selecting a pre-generation event under the generation event, and setting a command line in the generated event as copy $ (solution dir) lib\lib\dll $ (OutDir);
and setting a command behavior shell command, namely copying all the dll files under the SolutionDir directory into an output directory of the command behavior shell command, wherein a plurality of commands can be set, and copying the designated dll files or other files corresponding to the dll (the pdb program database files or the exp export library files).
And S8, directly running the solution after modifying the DLL, and calling by the demo at the moment to be the latest DLL content.
A system for verifying a demo and a link library by one key of vs2008, wherein the system comprises a scheme generating module, a starting item setting module, a dependent item setting module, an output catalog setting module, a header file output module, a LIB one-key verification module and a DLL one-key verification module;
the scheme generating module is used for opening the solution of the DLL or LIB engineering by using vs2008 and dragging the generated demo engineering into the solution of the DLL or LIB engineering;
the starting item setting module is used for entering a solution attribute page, selecting a starting item under a general attribute, selecting a single starting item and designating the single starting item as a corresponding demo item name;
the dependency item setting module is used for entering a solution attribute page, selecting an item dependency item under a general attribute, selecting a corresponding demo item name, and setting the dependency item as a corresponding DLL or LIB item name;
the output catalog setting module is used for entering attribute pages of DLL or LIB engineering, setting an output catalog, and generating a compiled DLL or LIB library into a LIB folder;
the header file output module is used for entering a property page of DLL or LIB engineering, setting a command line and outputting all header files to an include folder;
the LIB one-key verification module is used for entering an attribute page of the amo-removing project, adding a directory in an additional library directory, introducing a LIB library corresponding to the LIB, directly running a solution after modifying the LIB at the moment, calling by the amo at the moment to be the latest LIB content, and continuously entering the DLL one-key verification module if the LIB library corresponding to the DLL is introduced;
the DLL one-key verification module is used for entering an attribute page of the demo project, setting a command line again, copying the DLL to an output directory before generating an exe file, and directly running a solution after modifying the DLL at the moment, wherein the demo call is the latest DLL content.
In one embodiment of the present invention, the scheme generating module is further specifically: the vs2008 is used to open the solution of the DLL or LIB project and to pull the generated demo project into the solution of the DLL or LIB project, which is the file of. sln, which is the file of.vcproj.
The output catalog setting module is further specifically: entering an attribute page of DLL or LIB engineering, selecting a convention under configuration attributes, fixedly setting an output catalog to be./ LIB/LIB, and generating a compiled DLL or LIB library into a LIB folder.
The header file output module is further specifically: and entering an attribute page of the DLL or LIB engineering, selecting a generated event in the generated events under the configuration attribute, setting a command line as copy $ (solutionDir) \lib\include, and outputting all header files into an include folder.
The LIB one-key verification module is further specifically: entering an attribute page of the demo project, selecting a routine in a linker under configuration attribute, adding $ (SolutionDir) LIB/LIB in an additional library catalog, introducing the LIB library corresponding to the LIB, and directly running a solution after modifying the LIB, wherein the latest LIB content is called by the demo.
The DLL one-key verification module is further specifically: entering an attribute page of the demo project, selecting a pre-generated event in the generated events under the configuration attribute, setting a command line as copy $ (SolutionDir) lib\lib · DLL $ (OutDir), copying DLL to an output directory before generating exe, and directly running a solution after modifying the DLL, wherein the call of demo is the latest DLL content.
In summary, according to the method and the system for verifying the demo and the link library by one key of vs2008 provided by the invention, through configuring the related attributes of the solution and the project and using the corresponding command line script, after modifying the LIB or the DLL by one key, the demo can directly run the processing scheme of the latest LIB or DLL content.
The foregoing description is only of the preferred embodiments of the invention, and all changes and modifications that come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.
Claims (12)
1. A method for verifying a demo and a link library by one key of vs2008, wherein the link library comprises a dynamic link library DLL and a static link library LIB, and the method comprises the following steps:
step S1, using vs2008 to open the solution of the DLL or LIB project, and dragging the generated demo project into the solution of the DLL or LIB project;
s2, entering a solution attribute page, selecting a starting item under a general attribute, selecting a single starting item, and designating the single starting item as a corresponding demo item name;
s3, entering a solution attribute page, selecting an item dependent item under a general attribute, selecting a corresponding demo item name, and setting the dependent item as a corresponding DLL or LIB item name;
s4, entering an attribute page of DLL or LIB engineering, setting an output catalog, and generating a compiled DLL or LIB library into a LIB folder;
s5, entering an attribute page of DLL or LIB engineering, setting a command line, and outputting all header files to an include folder;
s6, entering an attribute page of the demo project, adding a directory in an additional library directory, introducing a LIB library corresponding to the LIB, directly running a solution after modifying the LIB, calling by the demo at the moment to be the latest LIB content, and continuing to enter the step S7 if the LIB library corresponding to the DLL is introduced;
and S7, entering an attribute page of the demo project, setting a command line again, copying the DLL to an output directory before generating the exe file, and directly running the solution after modifying the DLL, wherein the call of demo is the latest DLL content.
2. The method for verifying a demo and a linked library by one-touch vs2008 according to claim 1, wherein step S1 is further specifically: the vs2008 is used to open the solution of the DLL or LIB project and to pull the generated demo project into the solution of the DLL or LIB project, which is the file of. sln, which is the file of.vcproj.
3. The method for verifying a demo and a linked library by one-touch vs2008 according to claim 1, wherein step S4 is further specifically: entering an attribute page of DLL or LIB engineering, selecting a convention under configuration attributes, fixedly setting an output catalog to be./ LIB/LIB, and generating a compiled DLL or LIB library into a LIB folder.
4. The method for verifying a demo and a linked library by one-touch vs2008 according to claim 1, wherein step S5 is further specifically: and entering an attribute page of the DLL or LIB engineering, selecting a generated event in the generated events under the configuration attribute, setting a command line as copy $ (solutionDir) \lib\include, and outputting all header files into an include folder.
5. The method for verifying a demo and a linked library by one-touch vs2008 according to claim 1, wherein step S6 is further specifically: entering an attribute page of the demo project, selecting a routine in a linker under configuration attribute, adding $ (SolutionDir) LIB/LIB in an additional library catalog, introducing the LIB library corresponding to the LIB, and directly running a solution after modifying the LIB, wherein the latest LIB content is called by the demo.
6. The method for verifying a demo and a linked library by one-touch vs2008 according to claim 1, wherein step S7 is further specifically: entering an attribute page of the demo project, selecting a pre-generated event in the generated events under the configuration attribute, setting a command line as copy $ (SolutionDir) lib\lib · DLL $ (OutDir), copying DLL to an output directory before generating exe, and directly running a solution after modifying the DLL, wherein the call of demo is the latest DLL content.
7. A system for verifying a demo and a link library by one key of vs2008 is characterized by comprising a scheme generating module, a starting item setting module, a dependent item setting module, an output catalog setting module, a head file output module, a LIB one-key verification module and a DLL one-key verification module;
the scheme generating module is used for opening the solution of the DLL or LIB engineering by using vs2008 and dragging the generated demo engineering into the solution of the DLL or LIB engineering;
the starting item setting module is used for entering a solution attribute page, selecting a starting item under a general attribute, selecting a single starting item and designating the single starting item as a corresponding demo item name;
the dependency item setting module is used for entering a solution attribute page, selecting an item dependency item under a general attribute, selecting a corresponding demo item name, and setting the dependency item as a corresponding DLL or LIB item name;
the output catalog setting module is used for entering attribute pages of DLL or LIB engineering, setting an output catalog, and generating a compiled DLL or LIB library into a LIB folder;
the header file output module is used for entering a property page of DLL or LIB engineering, setting a command line and outputting all header files to an include folder;
the LIB one-key verification module is used for entering an attribute page of the amo-removing project, adding a directory in an additional library directory, introducing a LIB library corresponding to the LIB, directly running a solution after modifying the LIB at the moment, calling by the amo at the moment to be the latest LIB content, and continuously entering the DLL one-key verification module if the LIB library corresponding to the DLL is introduced;
the DLL one-key verification module is used for entering an attribute page of the demo project, setting a command line again, copying the DLL to an output directory before generating an exe file, and directly running a solution after modifying the DLL at the moment, wherein the demo call is the latest DLL content.
8. The system for one-click authentication of a demo and a linked library through vs2008 of claim 7, wherein the schema generation module is further specifically configured to: the vs2008 is used to open the solution of the DLL or LIB project and to pull the generated demo project into the solution of the DLL or LIB project, which is the file of. sln, which is the file of.vcproj.
9. The system for one-touch verification of a demo and a linked library by vs2008 of claim 7, wherein the output catalog setup module is further embodied as: entering an attribute page of DLL or LIB engineering, selecting a convention under configuration attributes, fixedly setting an output catalog to be./ LIB/LIB, and generating a compiled DLL or LIB library into a LIB folder.
10. The system for verifying a demo and a linked library by one-touch vs2008 of claim 7, wherein the header output module is further specifically configured to: and entering an attribute page of the DLL or LIB engineering, selecting a generated event in the generated events under the configuration attribute, setting a command line as copy $ (solutionDir) \lib\include, and outputting all header files into an include folder.
11. The system for one-key authentication of a demo and a linked library by vs2008 of claim 7, wherein the LIB one-key authentication module is further specifically: entering an attribute page of the demo project, selecting a routine in a linker under configuration attribute, adding $ (SolutionDir) LIB/LIB in an additional library catalog, introducing the LIB library corresponding to the LIB, and directly running a solution after modifying the LIB, wherein the latest LIB content is called by the demo.
12. The system for one-touch authentication of a demo and a linked library by vs2008 of claim 7, wherein the DLL one-touch authentication module is further embodied as: entering an attribute page of the demo project, selecting a pre-generated event in the generated events under the configuration attribute, setting a command line as copy $ (SolutionDir) lib\lib · DLL $ (OutDir), copying DLL to an output directory before generating exe, and directly running a solution after modifying the DLL, wherein the call of demo is the latest DLL content.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310275551.8A CN116301897A (en) | 2023-03-21 | 2023-03-21 | Method and system for verifying demo and link library through vs2008 one-key |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310275551.8A CN116301897A (en) | 2023-03-21 | 2023-03-21 | Method and system for verifying demo and link library through vs2008 one-key |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116301897A true CN116301897A (en) | 2023-06-23 |
Family
ID=86779406
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310275551.8A Pending CN116301897A (en) | 2023-03-21 | 2023-03-21 | Method and system for verifying demo and link library through vs2008 one-key |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116301897A (en) |
-
2023
- 2023-03-21 CN CN202310275551.8A patent/CN116301897A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7437715B2 (en) | System and method for generating a set of robot commands based on user entry events in a user interface | |
| US8201143B2 (en) | Dynamic mating of a modified user interface with pre-modified user interface code library | |
| JP2795244B2 (en) | Program debugging system | |
| US8176466B2 (en) | System and method for generating an application fragment | |
| Flannagan | JavaScript: the definitive guide | |
| US8607208B1 (en) | System and methods for object code hot updates | |
| CN101078987B (en) | Method, device and system for establishing customizable wrappers for web applications | |
| Leotta et al. | Pesto: Automated migration of DOM‐based Web tests towards the visual approach | |
| US20070174824A1 (en) | Techniques for generating and executing browser-hosted applications | |
| US7131111B2 (en) | Development of manifest for java embedded server bundle | |
| CN101866315B (en) | Test method and system of software development tool | |
| US9965257B2 (en) | Automatic configuration of project system from project capabilities | |
| CN111708528A (en) | Method, device and equipment for generating small program and storage medium | |
| Gallant | WebAssembly in action: with examples using C++ and Emscripten | |
| Verma | Mobile Test Automation With Appium | |
| Heffelfinger | Java EE 7 Development with NetBeans 8 | |
| KR20060120670A (en) | System and method for building software suite | |
| Yuan et al. | JBoss seam: simplicity and power beyond Java EE | |
| CN116301897A (en) | Method and system for verifying demo and link library through vs2008 one-key | |
| Price | C# 7.1 and. NET Core 2.0–Modern Cross-Platform Development: Create powerful applications with. NET Standard 2.0, ASP. NET Core 2.0, and Entity Framework Core 2.0, using Visual Studio 2017 or Visual Studio Code | |
| Narayn | Just React | |
| Salter et al. | NetBeans IDE 8 Cookbook | |
| CN114564195A (en) | Secondary development method of cloud CAD platform based on B/S architecture | |
| Kimmel et al. | Excel 2003 VBA Programmer's Reference | |
| Abbruzzese | Hands-On TypeScript for C# and. NET Core Developers: Transition from C# to TypeScript 3.1 and build applications with ASP. NET Core 2 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |