xous-core/utralib/src/generated.rs
bunnie 002a621181 change order of imports (work around rust-analyzer bug?)
I can't figure out why rust-analyzer on my system isn't work
correctly but if I change the order of imports things work better.

If this breaks things for Foundation Devices (@eupn) let me know,
I will poke at this some more and try to figure it out. In theory
it should have no impact but somehow I'm getting the atsamd target
*always* live in my vscode environment, even when it is switched
off when it isn't the last target in the list (and this overrides
all of the rust-analyzer settings for other targets).
2024-01-21 01:10:46 +08:00

56 lines
1.3 KiB
Rust

// Feature flags are checked inside build.rs for sanity, so we
// can use them here assuming all targets are mutually exclusive.
#[cfg(feature = "precursor-perflib")]
#[rustfmt::skip]
mod precursor_perf;
#[cfg(feature = "precursor-perflib")]
#[rustfmt::skip]
pub use precursor_perf::*;
#[cfg(feature = "precursor-dvt")]
#[rustfmt::skip]
mod precursor_dvt;
#[cfg(feature = "precursor-dvt")]
#[rustfmt::skip]
pub use precursor_dvt::*;
#[cfg(feature = "renode")]
#[rustfmt::skip]
mod renode;
#[cfg(feature = "renode")]
#[rustfmt::skip]
pub use renode::*;
#[cfg(feature = "precursor-pvt")]
#[rustfmt::skip]
mod precursor_pvt;
#[cfg(feature = "precursor-pvt")]
#[rustfmt::skip]
pub use precursor_pvt::*;
#[cfg(feature = "cramium-soc")]
#[rustfmt::skip]
mod cramium_soc;
#[cfg(feature = "cramium-soc")]
#[rustfmt::skip]
pub use cramium_soc::*;
#[cfg(feature = "cramium-fpga")]
#[rustfmt::skip]
mod cramium_fpga;
#[cfg(feature = "cramium-fpga")]
#[rustfmt::skip]
pub use cramium_fpga::*;
#[cfg(feature = "atsama5d27")]
#[rustfmt::skip]
mod atsama5d27;
#[cfg(feature = "atsama5d27")]
#[rustfmt::skip]
pub use atsama5d27::*;
// Hosted mode includes nothing, as it relies on the abstract host
// architecture for I/O; so this file is empty when the "hosted"
// configuration is selected and there are no corresponding "hosted"
// mode feature flags.