KR100878044B1 - Application translating method for providing compatible BREW and WIPI and device thereof - Google Patents

Abstract

A method and apparatus for compatibility between brew and wickies is disclosed. According to an aspect of the present invention, in a method of converting a project file input by a compatible device to provide compatibility between the WIPI and BREW platforms, extracting a source file of a specific format of the input project file. step; Analyzing a header of the source file to extract a supportable library according to the target platform from among the conversion libraries; And generating a conversion source file by converting the source file using the library. According to the present invention, there is provided a method and apparatus for converting an application for providing compatibility between a brew and a wiki which generates an application source and a resource according to another platform by using a source and a resource of an application produced by any one of the brew and a ppi. Can be.

BREW, WIPI, Platform, Terminal

Description

Application translating method for providing compatible BREW and WIPI and device

1 is a view schematically showing the configuration according to the function of the device for the compatibility of brew and wickie according to an embodiment of the present invention.

2 is a diagram illustrating a source analysis process according to an embodiment of the present invention.

3 through 5 illustrate project files according to an embodiment of the present invention.

6 is a flowchart illustrating a process of a source converter of a compiler unit according to an exemplary embodiment of the present invention.

7 illustrates an example of event processing in an event handler of a compatible device according to an embodiment of the present invention.

8 is a diagram illustrating the rate of change of BREW, WIPI-C, WIPI-Java according to an embodiment of the present invention.

9 is a diagram illustrating a process of generating an application corresponding to a target platform by analyzing a project file input by a compatible device according to an embodiment of the present invention.

<Description of the symbols for the main parts of the drawings>

100: compatible device

110: compiler

112, source analyzer 114: preprocessor 116: source converter

130: conversion library unit

132: BREW to WIPI Conversion Library

134: WIPI to BREW Conversion Library

136: C ++ to C Conversion Library

150: resource processing unit

152: Image Converter 154: Sound Converter

The present invention relates to compatibility between heterogeneous platforms, and more particularly, to a method and apparatus for converting an application for providing compatibility between brews and wickies.

Wippy is an acronym for the English word Wireless Internet Platform for Interoperability. In order to reduce national waste by allowing mobile operators to use the same platform, it has been promoted as a national project since 2001 in Korea. The wireless internet platform refers to basic software that functions as an operating system (OS) of a personal computer in a mobile phone terminal.

Since Korean mobile operators have made and used wireless Internet platforms in different ways, content providers have no choice but to make the same content into multiple platforms. Therefore, various unnecessary wastes occurred due to content creation and service, and Wi-Fi was created to reduce such wastes at the national level.

Brew is a platform developed by Qualcomm for code division multiple access (CDMA) mobile communications. Just like a desktop computer, it provides a convenient environment for downloading, updating, saving, and deleting programs on a mobile phone, as well as accessing e-mail, simple messages, real-time browsing, conversations, and group games. Unlike Java-based platforms, users can download and write the software they want directly on their devices.It is a technology standard in the mobile content field that causes a lot of problems due to different platforms. Doing.

The Wipy and the brew are different from each other, the application of the brew method is not executed by the terminal to which the Wippy is applied, and similarly, the Wipy method cannot be executed by the terminal to which the Brew is applied. In other words, in order to generate an application program according to Wifi and Brew, source code writing and compilation are executed in different environments. Therefore, the application developer was inconvenient to produce each source code corresponding to the brew and the Wi-Fi even for an application that performs the same function.

Accordingly, the present invention has been made to solve the above-described problem, and the compatibility between the brew and the Wi-Fi to generate an application source or resource according to the other platform using the source or resource of the application produced by any one of the Brew and Wi-Fi To provide an application conversion method and apparatus for providing.

In addition, the present invention automatically generates an application according to another platform using either the application according to the brew or the application according to the Wi-Fi, development efficiency that does not require the developer to perform a manual operation for a long time as before An object of the present invention is to provide an application conversion method and apparatus for providing compatibility between a brew and a wigee capable of providing a.

Other objects of the present invention will become more apparent through the preferred embodiments described below.

According to an aspect of the present invention for achieving the above object, in the conversion method of the project file input the compatible device to provide compatibility between the WIPI and BREW platform, the specific of the input project file Extracting a source file of a format; Analyzing a header of the source file to extract a supportable library according to a target platform from among conversion libraries; And a method of converting the source file using the library to generate a conversion source file, and a recording medium having recorded thereon a program for executing the method.

According to another aspect of the present invention for achieving the above object, in the apparatus for converting the input project file to provide compatibility between the WIPI and BREW platform, corresponding to the Wi-Fi and Brew platform A conversion library unit including a library, the conversion library including a conversion library for source conversion between the Wi-Fi and Brew; Extracting a source file of a specific format of a project file, analyzing a header of the source file, extracting a supportable library according to a target platform among the conversion libraries, and converting the source file using the extracted library; An application conversion apparatus including a compiler unit for generating a conversion source file is provided.

As the invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

Terms including ordinal numbers such as first and second may be used to describe various components, but the components are not limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component. The term and / or includes a combination of a plurality of related items or any item of a plurality of related items.

When a component is referred to as being "connected" or "connected" to another component, it may be directly connected to or connected to that other component, but it may be understood that other components may be present in between. Should be. On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that there is no other component in between.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art and shall not be construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings, and in describing the present invention with reference to the accompanying drawings, the same or corresponding elements are denoted by the same reference numerals regardless of the reference numerals, and duplicates thereof. The description will be omitted.

1 is a view schematically showing the configuration according to the function of the device for the compatibility of the brew and Wipy according to an embodiment of the present invention, Figure 2 is a view showing a source analysis process according to an embodiment of the present invention 3 to 5 are diagrams illustrating project files according to an embodiment of the present invention.

Referring to FIG. 1, an apparatus 100 (hereinafter referred to as a compatible apparatus) that provides compatibility between a brew and a Wippy according to the present embodiment includes a compiler unit 110, a conversion library unit 130, and a resource processing unit 150.

Here, the compatible device 100 does not necessarily need to be implemented in hardware, but may be implemented in software such as a program that can be installed and executed in a computer.

In order for the compatible device 100 to convert an application source or resource according to a brew and a Wi-Fi, three factors should be considered.

First, platform-specific library analysis and cross-platform library comparison, conversion, and implementation. For example, it is analysis of function API (Application Programming Interface) list or resource list used for application development.

Secondly, it is a method of processing and converting resources of an application program. For example, how to handle image resources such as BAR used in brews.

Third is the method of source conversion in terms of language. The linguistic transformation focuses on satisfying the syntax or semantic transformation of the language, rather than the execution of the translated source. This can be achieved by satisfying the steps of a traditional compiler. For example, WIPI_Java converts it to C ++.

According to the present embodiment, in the first case, the API conversion may be performed using a wrapper (ie, a conversion library). In the second case, conversion of image format, size, color, etc., and conversion of sound sources such as mp3, wav, and mmf are applicable. The third is source conversion from BREW C to WIPI C (or WIPI C to BREW C), and from WIPI_Java to BREW C ++.

The conversion library unit 130, the resource processing unit 150, and the compiler unit 110 are components for performing the above three elements. The conversion library unit 130 and the compiler unit 110 are closely related to the Wi-Fi and the brew, and the detailed function module can be designed through the previous analysis of the platform. Source analysis can be performed by analyzing the corresponding project file (which may be an application) for source conversion to find out what files are included in or referenced by the project. The source converter 116 of the compiler unit 110 performs source conversion between platforms using the 'BREW to WIPI conversion library' and 'WIPI to BREW conversion library'. In particular, the compiler unit 110 functions as a language-specific compiler region in conjunction with the conversion library unit 130 and the resource processing unit 150 in a functional aspect.

Hereinafter, the functions of the components of the compatible device 100 will be described.

As shown in the drawing, the compiler unit 110 of the compatible device 100 may include a source analyzer 112, a preprocessor 114, and a source converter 116.

The source analyzer 112 analyzes a corresponding project file for source conversion and extracts a file included in or referenced by the project.

The type of project being processed by the source analyzer 112 is, for example, Microsoft's Visual Studio project file for BREW (hereinafter MSVC), KTF Integrated SDK project for WIPI_C, WIPI_Java. Files (hereinafter referred to as KIS). Hereinafter, for convenience of description, it will be described on the assumption that two kinds of the above-described MSVC and KIS exist.

Referring to FIG. 2, project files serving as input parameters of the source analyzer 112 are project files of MSVC and project files of KIS. By the way, the project file of MSVC. The .prj file, a project file of dsw and KIS, commonly refers to a .dsp file.

In other words, the file containing the list of sources used or referenced in the project is the project file. I use .dsp files in common, not dsw and .prj files. Therefore, to get the list of source files included in the project, the actual analysis of the .dsp file is used. The .dsw and .prj files are used to get the location and file name of the .dsp file.

Examples of .dsw files, .prj files, and .dsp files are shown in FIGS.

3 and 4, it can be seen that the source list constituting the project does not exist in the .dsw file and the .prj file.

If the project file is a .dsw file, the line corresponding to the following code among the contents of the .dsw file is first searched using a keyword called project.

[Project: "jumpse" = ". ＼Jumpse.dsp"-Package Owner = <4>]

Next, find the ". \ Jumpse.dsp" entry using "project name" as a keyword, and separate directories and files using "＼" as a keyword. Then, the full path name of the .dsp file is returned, and the source list is extracted by analyzing the .dsp file.

On the other hand, if the project file is a .prj file, it is in xml format, but .prj and .dsp can be used without having to create an xml file because they are composed of the same project name in the same directory.

First, get the project folder name and project name by using the <PRJ_HOME> and <PRJ_NAME> tags in the .prj file.

[<PRJ_HOME> C: ＼Trans＼jumpse </ PRJ_HOME>

<PRJ_NAME> jumpse </ PRJ_NAME>]

Next, check whether the folder name, project name, .dsp file exists, return the full path name of the .dsp file, and analyze the .dsp file to extract the source list.

Also, if the project file is a .dsp file, the process of extracting the line with the source list by using the keyword "Source =" and separating the directory and the file by using "＼" as a keyword. Here, "＼" means the same directory as the directory where the .dsp file is located. After that, it returns the full path name of the source.

Referring back to FIG. 1, the preprocessor 114 is a module that parses and processes header files for the BREW and WIPI_C translation libraries.

Header file analysis and processing for the conversion library is a procedure to analyze the available (or unusable) functions by analyzing platform-supportable libraries generated during source conversion, and the header file is commented on the include file. And comments, and the associated source adds a header file to support the wrapper.

The WIPI platform supports some of the standard C library functions. These functions include the string.h, stdlib.h, stdarg.h, and time.h files. However, the BREW platform does not support standard C library functions, so it cannot be used. If you include the relevant header file, an error occurs at the link point, so all the header files declared by WIPI are commented out.

In order to explain the header file analysis and processing, in order to convert WIPI C to BREW C, it is necessary to determine whether the include file is supported and process the unsupported files. The analysis and processing procedures are as follows.

First, it analyzes and creates DB for (non) standard C library include files. That is, it is created with reference data of BREW to WIPI library and WIPI to BREW library. Afterwards, the target file list analysis of the project folder is performed, and the files available and impossible through the DB are converted to WIPI C-> BREW C (or BREW C-> WIPI C, replaced by the following transformation) through the library DB created. Check it. Comment out and add comments to the impossible include file, and add a header file ("W2BE.h") to use the wrapper.

The source converter 116 converts the BREW source into a state in which the BREW source is driven in the WIPI environment and the WIPI_C in the BREW environment by using the 'BREW to WIPI conversion library' and 'WIPI_C to BREW conversion library'. In addition, the source converter 116 is a module for performing source conversion between platforms in which WIPI_Java is changed to a state in which the WIPI_Java can be run in the BREW environment using the WIPI_Java to C ++ converter.

A wrapper is a transformation library that implements the same functionality in a form that is similar to the environment in which the API used in the original source is executed. Through this, the source code written for BREW can be built with the conversion wrapper so that it can be executed on the terminal equipped with WiPI (or WIPI source code can be executed on the BREW terminal). support). However, the items provided in the original environment are not included in the conversion target environment.

For this reason, it is not possible to implement all APIs provided by the WIPI platform as a conversion library on the BREW platform (or implement all APIs provided by the BREW platform as a conversion library on the WIPI platform), and thus, in the source converter 116 Not only is it required to handle APIs that cannot be converted, but also features that must be supported depending on the characteristics of the platform.

One such feature is the handling of global variables.

6 is a flowchart illustrating a process of a source converter of a compiler unit according to an embodiment of the present invention.

Referring to FIG. 6, in step 610, the wrapper processing module of the source converter 116 registers a token of the wrapper using a .csv file, and generates a wrapper support and a non-supportable table. The wrapper utility module sets the scope for comment processing and generates a list of used wrapper sources when the unsupported API is placed inside a function clause (if, switch, etc.) or loop clause (for, while, etc.).

If the conversion type is Wipy to Brew, in step 620, the global variable processing module of the source converter 116 registers global variable processing tokens such as Define, extern, and struct, and analyzes global variables and blocks for global variables. Define. In addition, the global variable processing module creates intermediate files for global variable conversion (for example, .tmp1, .tmp2, etc.) and annotates the global variable block. The process then proceeds to step 640.

If the conversion type is Brew to Wipy, in step 630, the PRJ generation module of the source converter 116 analyzes the project environment and generates a project environment value and an Xml-based .prj file.

In step 640, the DSP generation module of the source converter 116 generates dsp environment analysis and environment values, and generates conversion source and wrapper list information. In addition, the DSP generation module generates a .dsp file using environment values and list information.

Subsequently, in step 650, the conversion processing module of the source converter 116 generates a conversion source and a conversion report in which the header processing, the global variable processing, and the conversion non-convertable item are completed in the original source.

In this case, analysis and processing of possible APIs should be performed for replacing a conversion library for relevant APIs at the time of source conversion. First, source converter 116 analyzes the list of target files in the project folder, analyzes the conversion library supportable APIs, and creates a DB. That is, the source converter 116 writes the reference data of the BREW to WIPI library and the WIPI to BREW library, which can be updated later. In addition, the source converter 116 analyzes the API and related variables in the conversion source file, and performs commenting and commenting on impossible APIs and variables.

For example, according to the wrapper library API inspection and processing, when the WIPI source before conversion is "... M_Int32 currentMode = MC_imGetCurrentMode (); ...", it may be converted into the following BREW source.

"...

// WC2B-Disabled API

// M_Int32 currentMode = MC_imGetCurrentMode (); ... "

Unlike the WIPI platform, the transform processing module does not allow global variable support. This can cause problems when converting a WIPI platform based source that uses global variables into a BREW platform based source.

Therefore, through global variable processing, global variables used in WIPI source should be set in a predefined structure, provide a way to access from BREW application, and must be initialized by predefined function.

To handle global variables, you must analyze the global variables of the WIPI source for conversion, add relevant variables to predefined structures and functions, and reflect them in the conversion source.

Therefore, the global variable processing module of the source converter 116 analyzes the target files of the WIPI project folder to create a global variable list, registers the variable in a predefined function for global variable substitution, and adds the variable to the conversion source. In other words, the predefined function can be initialized by creating W2Bgen.c and W2Bgen.h files and registering global variables. In addition, the global variable processing module replaces the global variable of the source for conversion and adds a comment.

The conversion library unit 130 of the compatible device 100 illustrated in FIG. 1 includes the conversion libraries as described above. The transformation library (ie, wrapper) is a function that enables the target platform environment to emulate the runtime environment and the platform-provided API that the original contents were provided in the source platform environment. As shown in the drawing, BREW Three types of functionality are required: to WIPI, WIPI to BREW, and C ++ to C.

Although not shown in FIG. 1, the conversion library unit 130 may further include an event handler and an API wrapper. The event handler of the conversion library unit 130 is configured to smoothly execute the configuration of the original source code in the target environment because the execution method or flow control of each platform has its own characteristics. In addition, the API wrapper is a library for using APIs provided by each platform in a target environment. The API wrapper is additionally written to correspond to a function of the same role or perform a required role.

Event handler is a module that composes the event to execute the configuration of source source code smoothly in the target environment because each platform's execution method or flow control is different. When an event occurs in WIPI or BREW platform, it is an event handler. Event Dispatcher receives and delivers it back to the application to configure event handling.

Event handlers can be divided into event handlers for WIPI and event handlers for BREW. The event handler for WIPI receives events from the WIPI platform and converts them into events that can be used by BREW applications. The basic events that occur on the WIPI platform are startClet, pauseClet, resumeClet, restart, destroyClet, and paintClet (refresh), which translate each event into an event that can be handled by the BREW application. To pass.

FIG. 7 illustrates an example of event processing in an event handler of a compatible device according to an embodiment of the present invention, and FIG. 8 illustrates changes in BREW, WIPI-C, and WIPI-Java according to an embodiment of the present invention. The illustrated figure.

Referring to FIG. 7, a basic event such as IShell, IModule, HelperFuncs, IApplet, IDisplay, etc. is generated to receive and start an event by receiving a startClet event generated when an application is executed in the WIPI platform and converting and delivering EVT_APP_START that can be used in BREW. Register callback function and send EVT_APP_START to BREW application

The API wrapper of the conversion library unit 130 is a library that is additionally written to correspond to a function of the same role or perform a required role as a library for using the API used in each platform in different environments. For example, it means a library having the same name as the BREW API written in the WIPI API, which will be referred to at run time in order for the BREW application to run on the WIPI platform.

API wrapper libraries are written in interface units for BREW, in functional units for WIPI-C, and in class units for WIPI-Java.

The conversion rates for total BREW, WIPI-C, and WIPI-Java are illustrated in FIG.

Referring back to FIG. 1, the BREW to WIPI conversion library 132 of the conversion library unit 130 refers to a library that provides an environment for operating a BREW application on the WIPI platform. The BREW to WIPI conversion library 132 implements each API used in BREW as an API of WIPI. Therefore, the conversion library cannot be written for the functions that are not supported on the WIPI platform or the Software Development Kit (SDK).

The WIPI to BREW conversion library 134 refers to a library that provides an environment for operating WIPI-C applications on the BREW platform. Therefore, the WIPI to BREW conversion library 134 implements each API used in WIPI as an API of BREW. Therefore, Wrapper library cannot be written on the BREW platform or for functions not supported by SDK.

The C ++ to C conversion library 136 refers to a library that provides an environment for operating WIPI Java applications on the BREW platform. Therefore, the C ++ to C conversion library 136 implements each API used in WIPI as an API of BREW. Therefore, the conversion library cannot be written on the BREW platform or for functions not supported by the SDK.

The resource processor 150 of the compatible device 100 may include an image converter 152 and a sound source converter 154.

The image converter 152 functions to automatically convert some of the image attributes to meet the specifications of the platform or the terminal in order to use the image used in BREW or WIPI on another platform. The image converter 152 has three functions such as image format conversion, image size conversion, and image color conversion.

The image format can be converted to BMP for JPEG, PNG (except animation) and BMP for WIPI to BREW, and for all formats except BCI format and SIS format for BREW to WIPI. . In the case of BCI, it is Qualcomm's own format, and in case of SIS, it uses NeoMtel's own format, so it cannot be converted arbitrarily and cannot support automatic conversion.In the case of the image format, BMP, Can be used after changing to a format such as PNG.

Conversion to an image format means conversion at the converter level, and whether or not it can be operated on a terminal is practically possible only when a decoder for JPEG and GIF is installed in the terminal in the case of JPEG and GIF. do.

Conversion of the image size means that the size of the original image is converted as specified. It can support both reduction and enlargement compared to the original size, but when converting a small image to a large image, the image may not be clearly displayed depending on the conversion ratio.

Image color conversion means converting a high-resolution image into a low resolution image. For 256 colors, a fixed palette is used, which uses a slightly different palette for each manufacturer. Must be present

The sound source converter 154 functions to convert the sound source into a format that can be used by the terminal. The format used in the terminal may be MMF, for example. For sound source conversion, only WAVE to MMF, MIDI to MMF, and MP3 to MMF are supported. In the case of MP3, convert MP3 to WAVE file first and then MMF. In the case of WAVE to MMF, the WAVE to MMF conversion library provided by Yamaha was provided and developed. Therefore, the conversion restrictions for WAVE to MMF are the same as those for the library provided by Yamaha.

9 is a diagram illustrating a process of generating an application corresponding to a target platform by analyzing a project file input by a compatible device according to an embodiment of the present invention.

Referring to FIG. 9, the compatible device 100 analyzes an input project file and extracts an original source included in operation 910. That is, as described above, the source analyzer 112 of the compatible device 100 extracts and analyzes the .dsp file to extract the original source included in the project file.

The compatible device 100 recognizes the platform according to the extracted original source and the target platform to be converted (step 920). Thereafter, the compatible device 100 analyzes the header file for the conversion library according to the original source, analyzes the library that can be supported for each platform, and processes the header file when it is necessary to add the header file (step 930).

Thereafter, the compatible device 100 generates a transform source from which the original source is converted using the corresponding wrapper (ie, the transform library) (step 940). That is, the compatible device 100 generates a conversion source in which header processing, global variable processing, and conversion for non-convertible items are completed in the original source using a wrapper according to BREW to WIPI or WIPI to BREW.

The compatible device 100 converts a resource (ie, image and / or sound source data) included in the project file into a format according to a corresponding platform (step 950). Since the method for converting resources has been described above, a detailed description thereof will be omitted. Here, step 950 may be performed in preference to all the above-described steps, and may not be performed if resources are not included.

The compatible device 100 compiles the conversion source to generate an application according to the target platform including the converted image / source data (step 960).

Accordingly, the compatible device 100 may convert an application written in BREW, WIPI-C, or WIPI-Java to be run on a WIPI or BREW platform.

The method of the present invention as described above may be implemented in a program and stored in a computer-readable recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.).

The present invention is not limited to the above embodiments, and many variations are possible by those skilled in the art within the spirit of the present invention.

As described above, according to the present invention, the application conversion for providing compatibility between the brew and the wiki to generate an application source and resources according to the other platform using the source and the resource of the application produced by any one of the brew and the ppi A method and apparatus can be provided.

In addition, the present invention can automatically generate an application according to the other platform using any one of the application according to the brew or the application according to the Wipi, there is no need for the developer to perform a manual operation for a long time as before There is an effect that can provide development efficiency.

Although described above with reference to a preferred embodiment of the present invention, those skilled in the art that various modifications of the present invention without departing from the spirit and scope of the invention described in the claims below And can be changed.

Claims (12)

In the application conversion method of the compatible device to provide compatibility between the WIPI and BREW platform, (a) extracting a source file of a specific format of the input project file; (b) analyzing a header of the source file to extract a supportable library according to a target platform among the conversion libraries; (c) classifying an API or variable which is not supported by analyzing an API or an variable of the source file; (d) converting the source file using the supportable library to generate a conversion source file; And (e) adding a replacement function or replacement variable to the conversion source file corresponding to the unsupported API or variable, The substitution function or substitution variable is an application conversion method, characterized in that for replacing the function or variable that supports only one platform of the two platforms on another platform. The method of claim 1, Compiling the conversion source file to generate an application program corresponding to the target platform. The method of claim 1, Converting the resources included in the project file into a predetermined format corresponding to the target platform. The method of claim 1, And said specific format is .dsp. The method of claim 1, And the conversion library comprises one or more of a BREW to WIPI library, a WIPI to BREW library, and a C ++ to C library. The method of claim 1, wherein step (b) comprises: Recognizing an application programming interface (API) of at least one source file supporting the conversion library; And Extracting a library according to the target platform for the API of the source file. The method of claim 1, One of the two platforms supports the handling of global variables and the other platform does not support the handling of global variables. The substitution function is an application conversion method, characterized in that for replacing the processing of the global variable. The method of claim 7, wherein The application conversion method is And replacing the global variable included in the source file with a predefined substitution variable. In the application conversion apparatus for converting the input project file to provide compatibility between the WIPI and BREW platform, A conversion library unit including a library applicable to both the Wi-Fi and the Brew platform and including a conversion library for source conversion between the Wi-Fi and Brew; And Extract a source file of a specific format of a project file, analyze a header of the source file, extract a supportable library according to a target platform among the conversion libraries, and convert the source file by using the extracted library to convert Include a compiler section to generate source files, The compiler unit analyzes an application programming interface (API) or a variable of the source file to distinguish an unsupportable API or variable, and adds a substitute function or substitute variable corresponding to the unsupported API or variable to the conversion source file. Further, wherein the substitution function or substitution variable is an application conversion device, characterized in that for replacing the function or variable that supports only one of the two platforms on the other platform function or variable. The method of claim 9, And the compiler unit compiles the conversion source file to generate an application program corresponding to the target platform. The method of claim 9, And a resource processing unit for converting a resource included in the project file into a predetermined format corresponding to the target platform. In order to perform the application conversion method of the compatible device to provide compatibility between the WIPI and BREW platforms, instructions executable by the digital reading device are tangibly implemented, and programs readable by the digital reading device are recorded. In the recorded recording medium, (a) extracting a source file of a specific format of the input project file; (b) analyzing a header of the source file to extract a supportable library according to a target platform among the conversion libraries; (c) classifying an API or variable which is not supported by analyzing an API or an variable of the source file; (d) converting the source file using the supportable library to generate a conversion source file; And (e) adding a substitution function or substitution variable corresponding to the unsupported API or variable to the conversion source file, The substitution function or substitution variable is a recording medium, characterized in that for replacing the function or variable that supports only one platform of the two platforms on another platform.

Images