try to run c_wavloader in 0.6.2

[neojjm]

Hi~!! i try to make some application same as c_wavLoader in 0.6.2 but i have one problem that the application(same as wavloader) cant sad files....

In c_wavLoader.... CF::FileManager?_ptr _DM_fm = domMgr->fileMgr(); CF::FileSystem::FileInformationSequence?* result = _DM_fm->list("/waveforms/*.sad.xml" ); int cnt = result->length(); printf("result: %ld\n", cnt); ================================================================== I don't know how to work file-find "list" function? what's the find-start path?

[balister]

In the 0.6 branch, and upcoming 0.7 release, the Filemanager list method basically does a recursive directory search for the pattern passed in the arguments. It has no sense of paths.

A quick look at the code makes me wonder if c_wavloader ever worked with the 0.6.2 framework, even though someone created an 0.6.2 branch in c_wavloader.

Maybe one of the current OSSIE team members has more current information.

[shereef]

While the FileSystem? 'list' function should be recursive, it is not. It simply iterates through subdirectories of the root path (which is '/sdr' for 0.6.x and the upcoming 0.7.x). Also, we do not currently implement regular expression pattern matching (see line 408 of 'FileSystem?_impl.cpp'), but we're hoping to resolve that in the near future. If you want to search for a "pattern", like a SAD file for instance, then simply pass the string "sad.xml" as a parameter.

In the future, the ticket system is not meant for questions. Please forward any questions/problems to the ossie-discuss listserv. However, considering this is a problem that needs to be addressed, I thank you for bringing it to our attention.

[balister]

FileSystem? list is not recursive. See the SCA spec. It performs simple pattern matching. This ticket documents a problem in the 0.6.2 framework in that the framework does meet the specified behavior. The behavior you are describing is the behavior implemented in OSSIE.

As part of my Master's work, I implemented the FileSystem? (and FileManager?) for OSSIE and had the vast majority of this code passing the JTAP tests (including the list method). c_wavloader was written to support this work, especially on embedded systems (where omnipython is a beast to build). I took a quick look at the branch created called "0.6.2" for c_wavloader. It does not look like much effort was spent trying to get c_wavloader to work with 0.6.2.

I think you would be best off using the tools supplied with 0.6.2 and not looking in the repository for things labeled "0.6.2".

[shereef]

Currently, our ALF tool replaces the functionality of c_wavloader, and provides you with a display of the running waveform. Is there any particular reason why you want to use c_wavloader instead?

[cdietric]

Fixed in r9571