Method, system and equipment for generating oil-gas exploration software and storage medium

Abstract

The invention provides a method, system and device for generating oil and gas exploration software and a storage medium, and the method comprises the steps: constructing a third-party library according to project requirements, and writing the information of the third-party library into a third-party library project configuration file to configure the third-party library; independently writing a project file for each project; compiling a generation tool according to the parallel generation options and the environment required for generating each project; and constructing a complete project according to the generation tool, the third-party library and the project file, and generating oil-gas exploration software based on the complete project. According to the method, a project management scheme supporting cross-platforms is adopted, development work is simplified, tools are automatically generated and released, the generation and release difficulty of Windows platform software is greatly reduced, meanwhile, the environment configuration work during development and software installation execution is reduced through an environment configuration tool, and the stability of product execution is guaranteed.

Description

Technical Field

[0001] The present invention relates to the field of exploration, and more specifically, to a method, system, electronic device and computer-readable storage medium for generating oil and gas exploration software. Background Art

[0002] GeoEast (integrated software system for processing and interpretation of ultra-large seismic data) software has long been available in Linux version, which has been widely used and well received by a large number of users. In actual applications, many oil production plants have equipment installed with Windows systems, and these devices also have a large number of application software installed. These oil production plant users have real needs for GeoEast software, but the Windows devices they are using cannot directly install Linux applications, and the changes in user operating habits brought about by equipment upgrades or operating system switches cannot be immediately accepted. Therefore, providing a Windows version of GeoEast software is an effective solution. Providing a Windows version can not only expand the scope of application and increase the number of users, but also compete for other similar software application markets and enhance the competitiveness of GeoEast software.

[0003] The software execution method on Windows system is somewhat different from that on Linux. For example, the runtime library of VC (Visual C++) is required, the dynamic library loaded during execution is preferentially loaded from the current directory of the executable program, and Windows is usually a single-machine single-user operation mode. There are also differences between Windows software installation and Linux. Generally, there is no environment that can be set up directly in Windows like executing the source command in Linux. Usually, it is necessary to configure environment variables, add the path where the dependent module is located, or other environment variables required during execution. In order to cope with the changes in the Windows development and execution environment, as well as the subsequent expansion of GeoEast software, it is very necessary to simplify the developers' work in project configuration, software generation and release, and configuration of the software debugging execution environment. Summary of the invention

[0004] In view of this, the purpose of the embodiments of the present invention is to propose a method, system, computer device and computer-readable storage medium for generating oil and gas exploration software. The present invention adopts a cross-platform project management solution to simplify the development work and automate the generation and release tools, which greatly reduces the difficulty of generating and releasing Windows platform software. At the same time, the environment configuration tool reduces the environment configuration work during development and software installation and execution, and ensures the stability of product execution.

[0005] Based on the above purpose, one aspect of an embodiment of the present invention provides a method for generating oil and gas exploration software, comprising the following steps: building a third-party library according to project requirements, and writing information of the third-party library into a third-party library project configuration file to configure the third-party library; writing a project file separately for each project; writing a generation tool according to parallel generation options and the environment required to generate each project; and building a complete project according to the generation tool, the third-party library and the project file, and generating oil and gas exploration software based on the complete project.

[0006] In some embodiments, building a third-party library according to project requirements includes: creating a new support directory, creating a corresponding directory for each third-party library under the support directory, and storing the header file, export library file and dynamic link library file of each third-party library in the corresponding directory respectively.

[0007] In some embodiments, writing the information of the third-party library into the third-party library project configuration file to configure the third-party library includes: creating a third-party library project configuration file under the support directory, and writing the header file path, debug library path and library name, and release library path and library name in the third-party library project configuration file respectively.

[0008] In some implementations, building a third-party library according to project requirements includes: establishing debugging and release library directories respectively under the support directory, and copying the dynamic libraries of the third-party library to the corresponding directories respectively.

[0009] In some implementations, writing a project file separately for each project includes: writing a project file for each module, and re-disassembling modules with cross-dependencies.

[0010] In some implementations, writing a project file for each project separately includes: writing an upper-level project file containing subprojects according to the directory structure, configuring the order in which dependent subprojects are generated, and writing an upper-level directory hierarchy according to the order.

[0011] In some embodiments, generating oil and gas exploration software based on the complete project includes: writing commands for setting environment variable parameters, and / or configuring database service startup commands.

[0012] Another aspect of an embodiment of the present invention provides a system for generating oil and gas exploration software, including: a construction module, configured to build a third-party library according to project requirements, and write information about the third-party library into a third-party library project configuration file to configure the third-party library; a project module, configured to write a project file for each project separately; a tool module, configured to write a generation tool according to parallel generation options and the environment required to generate each project; and an execution module, configured to build a complete project according to the generation tool, the third-party library and the project file, and generate oil and gas exploration software based on the complete project.

[0013] According to another aspect of an embodiment of the present invention, there is provided an electronic device, comprising: at least one processor; and a memory, wherein the memory stores computer instructions executable on the processor, and the instructions implement the steps of the above method when executed by the processor.

[0014] According to another aspect of the embodiments of the present invention, a computer-readable storage medium is provided, which stores a computer program that implements the above method steps when executed by a processor.

[0015] The present invention has the following beneficial technical effects: adopting a cross-platform project management solution simplifies development work, automates generation and publishing tools, greatly reduces the difficulty of generating and publishing Windows platform software, and at the same time, the environment configuration tool reduces the environment configuration work during development and software installation and execution, ensuring the stability of product execution. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other embodiments can be obtained based on these drawings without paying creative work.

[0017] Figure 1 A schematic diagram of an embodiment of a method for generating oil and gas exploration software provided by the present invention;

[0018] Figure 2 A flow chart of a method for generating oil and gas exploration software provided by the present invention;

[0019] Figure 3 An organizational chart constructed for the project modules provided by the present invention;

[0020] Figure 4 A schematic diagram of an embodiment of a system for generating oil and gas exploration software provided by the present invention;

[0021] Figure 5 A schematic diagram of the hardware structure of an embodiment of a computer device for generating oil and gas exploration software provided by the present invention;

[0022] Figure 6 A schematic diagram of an embodiment of a computer storage medium for generating oil and gas exploration software provided by the present invention. DETAILED DESCRIPTION

[0023] In order to make the objectives, technical solutions and advantages of the present invention more clearly understood, the embodiments of the present invention are further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0024] It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are for distinguishing two non-identical entities with the same name or non-identical parameters. It can be seen that "first" and "second" are only for the convenience of expression and should not be understood as limitations on the embodiments of the present invention. The subsequent embodiments will not explain this one by one.

[0025] The purpose of the present invention is to solve the problems of software generation and release and operating environment configuration after Linux software is transplanted to the Windows platform. The scheme of the present invention can simplify the transplantation and development work, improve the efficiency of software generation and release, reduce the difficulty of software development, and reduce execution errors after software installation.

[0026] A first aspect of the embodiments of the present invention provides an embodiment of a method for generating oil and gas exploration software. Figure 1 FIG. 2 is a schematic diagram of an embodiment of a method for generating oil and gas exploration software provided by the present invention. Figure 1 As shown, the embodiment of the present invention includes the following steps:

[0027] S1. Build a third-party library according to project requirements, and write information of the third-party library into a third-party library project configuration file to configure the third-party library;

[0028] S2. Prepare a separate project document for each project;

[0029] S3. Write build tools based on parallel build options and the environment required to build each project; and

[0030] S4. Build a complete project according to the generation tool, third-party library and project files, and generate oil and gas exploration software based on the complete project.

[0031] Figure 2 A flow chart of a method for generating oil and gas exploration software provided by the present invention, such as Figure 2 As shown, the embodiment of the present invention includes the steps of: building basic module information, building various project modules, using generation tools to generate software, publishing software, installing and executing the software.

[0032] A third-party library is built according to project requirements, and information of the third-party library is written into a third-party library project configuration file to configure the third-party library.

[0033] In the embodiment of the present invention, about 20 third-party libraries are used. First, these libraries need to be compiled and generated. The compilation methods of each third-party library are quite different, and each library needs to be processed separately according to its own method. Since the third-party library version is stable, it generally changes less after generation, and does not need to be generated repeatedly every time the product is released. Note that two versions, debug and release, must be generated.

[0034] In some embodiments, building a third-party library according to project requirements includes: creating a new support directory, creating a corresponding directory for each third-party library under the support directory, and storing the header file, export library file and dynamic link library file of each third-party library in the corresponding directory respectively.

[0035] Create a third-party library directory. Find a suitable directory, create a new support directory, and create a directory for each third-party library in the support directory. Put the header files, export library files, and dynamic link library files of each generated third-party library into the corresponding directories respectively. Note that in the library directory lib, debug and release libraries need to be placed separately.

[0036] In some embodiments, writing the information of the third-party library into the third-party library project configuration file to configure the third-party library includes: creating a third-party library project configuration file under the support directory, and writing the header file path, debug library path and library name, and release library path and library name in the third-party library project configuration file respectively.

[0037] In order to facilitate the subsequent reference of these third-party libraries, the information of the third-party libraries needs to be written into the project configuration file of the third-party libraries, which can simplify the work of other modules when referencing them later. Create a project configuration file in the support directory. In the configuration file, write the header file path, debug library path and library name, release library path and library name respectively. The configuration file can be written separately for each library, which is more flexible when used. You can also write a unified configuration in a unified way, which is more convenient for reference.

[0038] In some implementations, the construction of a third-party library according to project requirements includes: establishing debug and release library directories respectively under the support directory, and copying the dynamic libraries of the third-party library to the corresponding directories respectively. Establishing a dynamic library directory for a third-party library. You can establish debug and release library directories respectively under the support directory, and copy the dynamic libraries of the third-party library to the corresponding directories respectively, to facilitate the subsequent configuration of the execution path.

[0039] Write a separate project file for each project. Since the generated files in the original Linux project do not support cross-platform use, you need to write a separate project file for each project. When writing project files, use a cross-platform solution so that they can be shared under multiple operating systems and easily ported to other platforms. Write a project file for each module. If a module requires a third-party library, you can import the third-party library project configuration file.

[0040] Figure 3 The organizational structure diagram of the project module provided by the present invention is as follows: Figure 3 As shown, the project modules include data platform, plug-in platform, plug-in scenarios and applications. The data platform includes file IO, data module and driver module. The plug-in platform includes plug-in module, platform module and basic module. The plug-in scenarios include base map scenes and geological profile scenes. The applications include various application modules.

[0041] In some implementations, writing a project file for each project separately includes: writing a project file for each module, and re-disassembling modules with cross-dependencies. Since Windows modules have strict dependencies when they are generated, it is necessary to re-disassemble the modules with cross-dependencies in the original Linux to prevent cross-dependencies.

[0042] In some embodiments, the project file for each project is written separately, including: writing an upper-level project file containing subprojects according to the directory structure, configuring the order of generation of subprojects with dependencies, and writing the upper-level directory hierarchy according to the order of generation. Writing an upper-level project file containing subprojects according to the directory structure. Note that if there are dependencies between subprojects, the order of generation needs to be configured. There is also a dependency order between the upper-level directory hierarchies, which need to be written according to the order of generation.

[0043] Write the overall project file. The overall project file contains several major directories, which are arranged in the order of generation. The overall project file does not necessarily have to be a single file. For example, due to the special generation relationship between some modules in this project, the overall project file is divided into two.

[0044] Write a build tool based on the parallel build options and the environment required to build each project. In order to perform batch builds, you need to write a build tool. Visual Studio is generally used as a development tool under Windows. If you use it directly to build, it is cumbersome and cannot perform batch builds. Therefore, you need to write a separate build tool.

[0045] Write environment variable settings. Including third-party libraries, installation generation directory, basic development library directory, database directory and other settings. The third-party library directory is set to the directory created when building the third-party library. The installation directory can be set to a newly created empty directory. It is necessary to distinguish between debugging and release. The database directory is the installed database directory.

[0046] Write the build mode settings. The build tool supports setting the build mode in the form of parameters. Set the parallel build method. The default setting is parallel build to speed up the build. Add build parameters. In addition to the set build mode, the build parameters can also include custom parameters to control the build method, etc. Write the build process, which mainly includes the cleanup, build and installation processes.

[0047] Open the development tool command line, execute the generated tool, build the project, and generate the underlying module in about 20 minutes. View the generation results. Open the set installation directory, and you can see that all header files and library files have been generated in the directory respectively.

[0048] A complete project is built according to the generation tool and project files, and oil and gas exploration software is generated based on the complete project. The entire project has been built. However, if the executable program in the project is directly executed, errors such as library not found will be reported. Usually, the path needs to be manually configured to the system directory, which is a cumbersome and error-prone process. Therefore, it is necessary to write an environment configuration tool for one-click configuration.

[0049] In some embodiments, generating oil and gas exploration software based on the complete project includes: writing commands for setting environment variable parameters, and / or configuring database service startup commands.

[0050] Write commands to set environment variable parameters. Mainly include: third-party library directory, development framework library directory, database directory, execution environment PATH directory, license directory, etc. If it is a new environment, you also need to configure the database service startup command, etc. Execute the configuration tool set in the above steps to complete the one-click configuration of the execution environment, database service startup, etc. After completing the above steps, you can open the executable program in the installation location.

[0051] Use the packaging tool installmaker to package the generated software. Select the package file path, which is the location where the final packaged file is generated; select the packaged component, for example, you can select the directory generated by this project to create a component; execute the packaging, and after the packaging is completed, an executable program will be generated for release and installation.

[0052] After the user obtains the packaged installer, execute the installer to install the software. Execute the installer, select the installation directory, and execute the installation process; during the installation process, the one-click configuration tool will be executed to configure the environment, start the database service, and other processes, without the need for separate configuration by the user.

[0053] It should be pointed out in particular that the various steps in the various embodiments of the above-mentioned method for generating oil and gas exploration software can be cross-linked, replaced, added, and deleted. Therefore, these reasonable permutations, combinations and transformations of the method for generating oil and gas exploration software should also fall within the scope of protection of the present invention, and the scope of protection of the present invention should not be limited to the embodiments.

[0054] Based on the above purpose, the second aspect of the embodiment of the present invention provides a system for generating oil and gas exploration software. Figure 4 As shown, the system 200 includes the following modules: a construction module, configured to build a third-party library according to project requirements, and write the information of the third-party library into the third-party library project configuration file to configure the third-party library; a project module, configured to write a project file for each project separately; a tool module, configured to write a generation tool according to parallel generation options and the environment required to generate each project; and an execution module, configured to build a complete project according to the generation tool, the third-party library and the project file, and generate oil and gas exploration software based on the complete project.

[0055] In some embodiments, the construction module is configured to: create a new support directory, create a corresponding directory for each third-party library under the support directory, and store the header file, export library file and dynamic link library file of each third-party library in the corresponding directory respectively.

[0056] In some implementations, the construction module is configured to: create a third-party library project configuration file under the support directory, and respectively write the header file path, debug library path and library name, and release library path and library name in the third-party library project configuration file.

[0057] In some implementations, the construction module is configured to: establish debugging and release library directories respectively under the support directory, and copy the dynamic libraries of the third-party libraries to the corresponding directories respectively.

[0058] In some implementations, the project module configuration is used to: write a project file for each module, and re-disassemble modules with cross-dependencies.

[0059] In some implementations, the project module is configured to: compile an upper-level project file containing sub-projects according to a directory structure, configure the order in which dependent sub-projects are generated, and compile an upper-level directory hierarchy according to the order.

[0060] In some implementations, the execution module is configured to: write commands for setting environment variable parameters, and / or configure database service startup commands.

[0061] Based on the above purpose, the third aspect of an embodiment of the present invention proposes a computer device, including: at least one processor; and a memory, the memory storing computer instructions that can be run on the processor, the instructions being executed by the processor to implement the following steps: S1, building a third-party library according to project requirements, and writing the information of the third-party library into a third-party library project configuration file to configure the third-party library; S2, writing a project file separately for each project; S3, writing a generation tool according to parallel generation options and the environment required to generate each project; and S4, building a complete project according to the generation tool, the third-party library and the project file, and generating oil and gas exploration software based on the complete project.

[0062] In some embodiments, building a third-party library according to project requirements includes: creating a new support directory, creating a corresponding directory for each third-party library under the support directory, and storing the header file, export library file and dynamic link library file of each third-party library in the corresponding directory respectively.

[0063] In some embodiments, writing the information of the third-party library into the third-party library project configuration file to configure the third-party library includes: creating a third-party library project configuration file under the support directory, and writing the header file path, debug library path and library name, and release library path and library name in the third-party library project configuration file respectively.

[0064] In some implementations, building a third-party library according to project requirements includes: establishing debugging and release library directories respectively under the support directory, and copying the dynamic libraries of the third-party library to the corresponding directories respectively.

[0065] In some implementations, writing a project file separately for each project includes: writing a project file for each module, and re-disassembling modules with cross-dependencies.

[0066] In some implementations, writing a project file for each project separately includes: writing an upper-level project file containing subprojects according to the directory structure, configuring the order in which dependent subprojects are generated, and writing an upper-level directory hierarchy according to the order.

[0067] In some embodiments, generating oil and gas exploration software based on the complete project includes: writing commands for setting environment variable parameters, and / or configuring database service startup commands.

[0068] like Figure 5FIG. 1 is a schematic diagram of the hardware structure of an embodiment of the computer device for generating the oil and gas exploration software provided by the present invention.

[0069] As Figure 5 Taking the device shown as an example, the device includes a processor 301 and a memory 302.

[0070] The processor 301 and the memory 302 may be connected via a bus or other means. Figure 5 The example of connecting through bus is taken in the following.

[0071] The memory 302 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules, such as program instructions / modules corresponding to the method for generating oil and gas exploration software in the embodiment of the present application. The processor 301 executes various functional applications and data processing of the server by running the non-volatile software programs, instructions and modules stored in the memory 302, that is, realizing the method for generating oil and gas exploration software.

[0072] The memory 302 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required by at least one function; the data storage area may store data created according to the use of the method for generating oil and gas exploration software, etc. In addition, the memory 302 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 302 may optionally include a memory remotely arranged relative to the processor 301, and these remote memories may be connected to the local module via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0073] Computer instructions 303 corresponding to one or more methods of generating oil and gas exploration software are stored in the memory 302. When executed by the processor 301, the method of generating oil and gas exploration software in any of the above method embodiments is executed.

[0074] Any embodiment of a computer device that executes the above-mentioned method for generating oil and gas exploration software can achieve the same or similar effect as any corresponding embodiment of the above-mentioned method.

[0075] The present invention also provides a computer-readable storage medium, which stores a computer program for executing the method for generating oil and gas exploration software when executed by a processor.

[0076] like Figure 6FIG. 1 is a schematic diagram of an embodiment of a computer storage medium for generating oil and gas exploration software provided by the present invention. Figure 6 Taking the computer storage medium shown as an example, the computer readable storage medium 401 stores a computer program 402 that performs the above method when executed by a processor.

[0077] Finally, it should be noted that a person skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program of the method for generating oil and gas exploration software can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the storage medium of the program can be a magnetic disk, an optical disk, a read-only storage memory (ROM) or a random access memory (RAM), etc. The above-mentioned computer program embodiments can achieve the same or similar effects as the corresponding above-mentioned arbitrary method embodiments.

[0078] The above are exemplary embodiments disclosed in the present invention, but it should be noted that various changes and modifications may be made without departing from the scope disclosed in the embodiments of the present invention as defined in the claims. The functions, steps and / or actions of the method claims according to the disclosed embodiments described herein do not need to be performed in any particular order. In addition, although the elements disclosed in the embodiments of the present invention may be described or required in individual form, they may also be understood as multiple unless explicitly limited to the singular.

[0079] It should be understood that, as used herein, the singular forms "a", "an" are intended to include the plural forms as well, unless the context clearly supports an exception. It should also be understood that, as used herein, "and / or" refers to any and all possible combinations including one or more of the associated listed items.

[0080] The serial numbers of the embodiments disclosed in the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0081] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0082] A person skilled in the art should understand that the discussion of any of the above embodiments is only exemplary and is not intended to imply that the scope of the disclosure of the embodiments of the present invention (including the claims) is limited to these examples; under the concept of the embodiments of the present invention, the technical features in the above embodiments or different embodiments can also be combined, and there are many other changes in different aspects of the embodiments of the present invention as above, which are not provided in detail for the sake of simplicity. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present invention should be included in the protection scope of the embodiments of the present invention.

Claims

1. A method for generating oil and gas exploration software, characterized in that: The steps include: Build a third-party library according to project requirements, and write information about the third-party library into a third-party library project configuration file to configure the third-party library; Write a separate project document for each project; Write build tools with parallel build options and the environment needed to build each project; as well as A complete project is constructed according to the generation tool, third-party libraries and project files, and oil and gas exploration software is generated based on the complete project.

2. The method for generating oil and gas exploration software according to claim 1, characterized in that: The construction of third-party libraries according to project requirements includes: A new support directory is created, a corresponding directory is created for each third-party library under the support directory, and the header file, export library file and dynamic link library file of each third-party library are respectively stored in the corresponding directory.

3. The method for generating oil and gas exploration software according to claim 2, characterized in that: Writing the information of the third-party library into the third-party library project configuration file to configure the third-party library includes: A third-party library project configuration file is created in the support directory, and a header file path, a debug library path and a library name, and a release library path and a library name are respectively written in the third-party library project configuration file.

4. The method for generating oil and gas exploration software according to claim 2, characterized in that: The construction of third-party libraries according to project requirements includes: Create debugging and release library directories respectively under the support directory, and copy the dynamic libraries of the third-party libraries to the corresponding directories respectively.

5. The method for generating oil and gas exploration software according to claim 1, characterized in that: The separate project file for each project includes: Write project files for each module and re-disassemble modules with cross-dependencies.

6. The method for generating oil and gas exploration software according to claim 1, characterized in that: The separate project file for each project includes: Write the upper-level project file containing sub-projects according to the directory structure, configure the order in which the sub-projects with dependencies are generated, and write the upper-level directory hierarchy according to the order.

7. The method for generating oil and gas exploration software according to claim 1, characterized in that: The oil and gas exploration software generated based on the complete project includes: Write commands to set environment variable parameters and / or configure database service startup commands.

8. A system for generating oil and gas exploration software, characterized in that: include: A construction module is configured to build a third-party library according to project requirements, and write information of the third-party library into a third-party library project configuration file to configure the third-party library; Project module, configured to write project files for each project separately; Tools module, which is configured to write build tools based on parallel build options and the environment required to build each project; as well as An execution module is configured to build a complete project according to the generation tool, third-party library and project file, and generate oil and gas exploration software based on the complete project.

9. An electronic device, characterized in that: include: at least one processor; as well as A memory storing computer instructions executable on the processor, wherein the instructions, when executed by the processor, implement the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images